ConfluenceApplication · Atlassian
CVE-2017-18083
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 · uneditedThe editinword resource in Atlassian Confluence Server before version 6.4.0 allows remote attackers to inject arbitrary HTML or JavaScript via a cross site scripting (XSS) vulnerability through the contents of an uploaded file.
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 confidenceA stored cross-site scripting (XSS) vulnerability in the editinword resource of Atlassian Confluence Server versions before 6.4.0 allows remote attackers to inject arbitrary HTML or JavaScript through malicious content within uploaded files. This stored XSS executes when the file contents are rendered or processed by the application.
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
ConfluenceApplication
< 6.4.0CVSS 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.
-
Identify Confluence Server installation and versionCheck the Confluence administration console or run 'confluence --version' from the installation directory. Alternatively, view the about page in Confluence admin settings to find the exact version number.Affected if The installed Confluence Server version is lower than 6.4.0 (e.g., 6.3.x, 6.2.x, earlier versions).
-
Verify editinword resource accessibilityAttempt to access the editinword endpoint via the Confluence web interface or check if the /editinword path is available in the application routing. This is typically found in the attachment/macro functionality for Office documents.Affected if The editinword resource is accessible and the Confluence version is below 6.4.0.
-
Confirm file upload feature is enabledCheck Confluence global permissions and office editor settings in the administration console. Verify that users with appropriate permissions can upload Word documents (.docx, .doc) or other office files.Affected if File uploads are permitted and the editinword feature handles uploaded documents.
-
Inspect uploaded file handlingUpload a test file through Confluence and check if the editinword feature processes or renders the file content. Review server logs for any errors related to editinword or office connector processing.Affected if The editinword functionality processes uploaded files and the server runs a version prior to 6.4.0.
A Confluence Server installation is affected if it runs any version lower than 6.4.0 and has the editinword/office document editing feature accessible to users who can upload files.
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.4.0
Upgrade Confluence Server to version 6.4.0 or later to receive the patch. Alternatively, implement server-side input validation and sanitization on the editinword file upload functionality to neutralize malicious script content before processing.
Fix this in Confluence
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18083 — 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-2017-18083 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