CVE-2018-8928
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCross-site scripting (XSS) vulnerability in Address Book Editor in Synology CardDAV Server before 6.0.8-0086 allows remote authenticated users to inject arbitrary web script or HTML via the (1) family_name, (2) given_name, or (3) additional_name parameter.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCross-site scripting (XSS) vulnerability in Synology CardDAV Server's Address Book Editor allows remote authenticated users to inject arbitrary web script or HTML via the family_name, given_name, or additional_name parameters. This is a stored XSS vulnerability where malicious payloads are persisted in the address book and executed when other users view the contact.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.0.8-0086CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Synology CardDAV Server versionOpen Synology DSM, go to Package Center, find CardDAV Server, and note the installed version number. Alternatively, run 'sudo synopkg list' from command line and grep for CardDAV Server.Affected if The installed version is lower than 6.0.8-0086
-
Verify CardDAV Server is runningIn DSM, go to Package Center or Control Panel > Application Portal > CardDAV Server, and confirm the service status shows as Running.Affected if CardDAV Server is installed and running on a vulnerable version
-
Confirm Address Book Editor is enabledIn DSM, open CardDAV Server settings and check if any address books are configured under the Address Book Editor section. Look for any user-created or synced address books.Affected if Address Book Editor contains configured address books accessible to users
-
Inspect stored contacts for XSS payloadsAccess the CardDAV Server's underlying database or use a CardDAV client to export contacts. Search contact records for script tags, javascript: URIs, or HTML tags in the family_name, given_name, or additional_name fields.Affected if Any contact records contain unsanitized HTML or script content in the name fields that could execute when viewed
A user is affected if Synology CardDAV Server version is below 6.0.8-0086, the service is running with address books configured, AND malicious payloads exist in stored contact name fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data6.0.8-0086
Upgrade to Synology CardDAV Server version 6.0.8-0086 or later which includes proper input sanitization. As a temporary measure, implement server-side input validation and output encoding on the affected parameters.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8928 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-8928 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data