dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2024-21690

HIGH · 8.2 CVSS v3.1 Published 2024-08-21
Fix available
A fix is available. Upgrade to after 8.9.4 or later.
See remediation →
89/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
This High severity Reflected XSS and CSRF (Cross-Site Request Forgery) vulnerability was introduced in versions 7.19.0, 7.20.0, 8.0.0, 8.1.0, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 8.7.1, 8.8.0, and 8.9.0 of Confluence Data Center and Server. This Reflected XSS and CSRF (Cross-Site Request Forgery) vulnerability, with a CVSS Score of 7.1, allows an unauthenticated attacker to execute arbitrary HTML or JavaScript code on a victims browser and force a end user to execute unwanted actions on a web application in which they're currently authenticated which has high impact to confidentiality, low impact to integrity, no impact to availability, and requires user interaction. Atlassian recommends that Confluence Data Center and Server customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: * Confluence Data Center and Server 7.19: Upgrade to a release greater than or equal to 7.19.26 * Confluence Data Center and Server 8.5: Upgrade to a release greater than or equal to 8.5.14 * Confluence Data Center and Server 9.0: Upgrade to a release greater than or equal to 9.0.1 See the release notes (https://confluence.atlassian.com/doc/confluence-release-notes-327.html). You can download the latest version of Confluence Data Center and Server from the download center (https://www.atlassian.com/software/confluence/download-archives). This vulnerability was reported via our Bug Bounty program.

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 confidence

This is a combined Reflected XSS and CSRF vulnerability in Atlassian Confluence Data Center and Server. An unauthenticated attacker can inject arbitrary HTML or JavaScript into a victim's browser via reflected parameters, while also being able to force authenticated users to execute unwanted actions through CSRF. The attack requires user interaction.

MitigationUpgrade Confluence to version 7.19.26+, 8.5.14+, or 9.0.1+ as specified in Atlassian's advisory. Until upgrade, consider network-level restrictions and monitor for suspicious requests.

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
Affected:>= 7.19.0, <= 7.19.25>= 7.20.0, <= 7.20.3>= 8.0.0, <= 8.0.4>= 8.1.0, <= 8.1.4>= 8.2.0, <= 8.2.3>= 8.3.0, <= 8.3.4>= 8.4.0, <= 8.4.5>= 8.5.0, <= 8.5.12>= 8.6.0, <= 8.6.2>= 8.7.1, <= 8.7.2>= 8.8.0, <= 8.8.1>= 8.9.0, <= 8.9.4
Confluence ServerApplication
Affected:>= 7.19.0, <= 7.19.25>= 7.20.0, <= 7.20.3>= 8.0.0, <= 8.0.4>= 8.1.0, <= 8.1.4>= 8.2.0, <= 8.2.3>= 8.3.0, <= 8.3.4>= 8.4.0, <= 8.4.5>= 8.5.0, <= 8.5.12>= 8.6.0, <= 8.6.2>= 8.7.1, <= 8.7.2>= 8.8.0, <= 8.8.1>= 8.9.0, <= 8.9.4

CVSS 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
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Confluence product type
    Determine if the installation is Confluence Data Center or Confluence Server. Both product types are affected by this CVE.
    Affected if The product is Confluence Data Center or Server (both are affected)
  2. Find installed Confluence version
    Locate the installed version number through the administration console, the /about/confluence page, or startup logs. The version is typically displayed in the admin interface under 'General Configuration' or similar.
    Affected if The version cannot be determined or is not visible
  3. Compare version against affected ranges
    Check if the installed version falls within any of these affected ranges: 7.19.0-7.19.25, 7.20.0-7.20.3, 8.0.0-8.0.4, 8.1.0-8.1.4, 8.2.0-8.2.3, 8.3.0-8.3.4, 8.4.0-8.4.5, 8.5.0-8.5.12, 8.6.0-8.6.2, 8.7.1-8.7.2, 8.8.0-8.8.1, or 8.9.0-8.9.4
    Affected if The installed version matches any of the listed affected ranges

If Confluence Data Center or Server is running a version within the affected ranges listed above, the environment is vulnerable to the reflected XSS and CSRF attacks described in CVE-2024-21690.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 8.9.4
Interim mitigation

Upgrade Confluence to version 7.19.26+, 8.5.14+, or 9.0.1+ as specified in Atlassian's advisory. Until upgrade, consider network-level restrictions and monitor for suspicious requests.

Recommended fix High confidence

7.19.x -> 7.19.26+, 7.20.x -> 8.5.14+, 8.0-8.4.x -> 8.5.14+, 8.5.x -> 8.5.14+, 8.6-8.9.x -> 9.0.1+

  1. 1. Back up your Confluence database and home directory before upgrading
  2. 2. Download the appropriate fixed version from Atlassian's download center (https://www.atlassian.com/software/confluence/download-archives)
  3. 3. Stop the Confluence service
  4. 4. Run the installer or deploy the new WAR/EAR file according to standard Confluence upgrade documentation
  5. 5. Start the Confluence service and verify the upgrade was successful
  6. 6. Test critical functionality to ensure the upgrade did not break existing workflows
Caveat Review Confluence release notes for your target version for any known compatibility issues or deprecated features; major version jumps (e.g., 7.x to 8.x or 9.x) may require migration considerations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Confluence Data Center Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21690 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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