Confluence Data CenterApplication · Atlassian
CVE-2020-14175
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 · uneditedAffected versions of Atlassian Confluence Server and Data Center allow remote attackers to inject arbitrary HTML or JavaScript via a Cross-Site Scripting (XSS) vulnerability in user macro parameters. The affected versions are before version 7.4.2, and from version 7.5.0 before 7.5.2.
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 Atlassian Confluence Server and Data Center allows remote attackers to inject arbitrary HTML or JavaScript via user macro parameters. The vulnerability affects versions before 7.4.2 and versions 7.5.0 through 7.5.1.
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
Confluence Data CenterApplication
< 7.4.2>= 7.5.0, < 7.5.2
Confluence ServerApplication
< 7.4.2>= 7.5.0, < 7.5.2CVSS 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.1/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 the installed Confluence versionAccess the Confluence administration console and navigate to General Configuration, or run the command: confluence --version (if using Atlassian SDK). Locate the build number or version number displayed.Affected if The installed version is earlier than 7.4.2, or falls between 7.5.0 and 7.5.1 inclusive.
-
Confirm the Confluence deployment typeDetermine whether the deployment is Confluence Server (self-hosted) or Confluence Data Center from the administration overview screen.Affected if The instance is a Server or Data Center deployment (both affected, not Confluence Cloud).
-
Verify if user macros are in useNavigate to Confluence Admin > User Macros, or inspect the macros configuration directory. Look for any custom user macros that accept parameters from end users.Affected if User macros with parameter input fields are defined and accessible to users.
-
Check for unauthenticated or low-privilege user accessReview the Confluence user permissions and group memberships. Determine if non-admin users can create or edit content that utilizes user macro parameters.Affected if Unauthenticated remote users or low-privilege logged-in users can supply input to user macro parameters.
A user is affected if their Confluence version is < 7.4.2 or >= 7.5.0 but < 7.5.2, AND user macro parameters are accessible to remote or low-privilege users.
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 data7.4.27.5.2
Upgrade Confluence Server or Data Center to version 7.4.2, 7.5.2, or later to resolve the XSS vulnerability in user macro parameters.
Fix this in Confluence Data Center
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14175 — 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-2020-14175 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