Confluence Data CenterApplication · Atlassian
CVE-2021-39114
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 users with a valid account on a Confluence Data Center instance to execute arbitrary Java code or run arbitrary system commands by injecting an OGNL payload. The affected versions are before version 6.13.23, from version 6.14.0 before 7.4.11, from version 7.5.0 before 7.11.6, and from version 7.12.0 before 7.12.5.
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 confidenceOGNL injection vulnerability in Atlassian Confluence Server and Data Center allows authenticated users to execute arbitrary Java code or run arbitrary system commands by injecting malicious OGNL payloads. The vulnerability affects specific version ranges before 6.13.23, 6.14.0-7.4.10, 7.5.0-7.11.5, and 7.12.0-7.12.4.
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
< 6.13.23>= 6.14.0, < 7.4.11>= 7.5.0, < 7.11.6>= 7.12.0, < 7.12.5
Confluence ServerApplication
< 6.13.23>= 6.14.0, < 7.4.11>= 7.5.0, < 7.11.6>= 7.12.0, < 7.12.5CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 installed Confluence versionCheck the Confluence version via the admin UI (Confluence Admin > General Configuration > Confluence Information) or by inspecting the confluence-version.properties file in the Confluence installation directoryAffected if The installed version is < 6.13.23, between 6.14.0-7.4.10, between 7.5.0-7.11.5, or between 7.12.0-7.12.4
-
Confirm Confluence deployment typeDetermine whether the instance is Confluence Server or Confluence Data Center. This can be found in the admin UI under General Configuration or by checking the installation license typeAffected if The instance is either Confluence Server or Confluence Data Center and the version matches the affected ranges from step 1
-
Verify network exposureDetermine if the Confluence instance is accessible from untrusted networks. Check firewall rules, reverse proxy configuration, and whether the instance is exposed to the internetAffected if The Confluence web interface is reachable from networks where untrusted authenticated users could attempt exploitation
-
Assess user authentication settingsReview the Confluence user management configuration to understand how users authenticate (internal directory, LDAP, SSO, etc.) and whether guest access or open registration is enabledAffected if There are authenticated user accounts (including guest or externally-provisioned users) who have access to Confluence and could inject OGNL expressions
The environment is affected if Confluence Server or Data Center is running a version within the ranges < 6.13.23, 6.14.0-7.4.10, 7.5.0-7.11.5, or 7.12.0-7.12.4 and the instance is accessible to authenticated 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.
dbcve · scoped6.13.237.4.117.11.6
Upgrade Confluence to version 6.13.23, 7.4.11, 7.11.6, 7.12.5 or later. If immediate patching is not feasible, restrict network access to Confluence instances and disable the account used for the attack vector.
Upgrade to Confluence 6.13.23, 7.4.11, 7.11.6, or 7.12.5 depending on your current version branch
- Back up the Confluence database and home directory before starting the upgrade
- Determine your current Confluence version from the About Confluence page or administration console
- Identify which version branch you are currently on (< 6.14.0, 6.14.x - 7.4.x, 7.5.x - 7.11.x, or 7.12.x)
- If on version < 6.14.0, upgrade directly to version 6.13.23
- If on version 6.14.x through 7.4.x, upgrade to version 7.4.11
- If on version 7.5.x through 7.11.x, upgrade to version 7.11.6
- If on version 7.12.x, upgrade to version 7.12.5
- After upgrading, verify the fix by checking the Confluence version says 6.13.23, 7.4.11, 7.11.6, or 7.12.5
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Confluence Data Center
Scoped from the published advisory
- Consultation4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-39114 — 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-2021-39114 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