dbcve.org
Confluence Data CenterApplication · Atlassian

CVE-2023-22526

HIGH · 8.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 7.19.17 / 8.5.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 RCE (Remote Code Execution) vulnerability was introduced in version 7.19.0 of Confluence Data Center. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 7.2, allows an authenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires no user interaction. Atlassian recommends that Confluence Data Center 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 7.19.17, or any higher 7.19.x release Confluence Data Center and Server 8.5: Upgrade to a release 8.5.5 or any higher 8.5.x release Confluence Data Center and Server 8.7: Upgrade to a release 8.7.2 or any higher release See the release notes ([https://confluence.atlassian.com/doc/confluence-release-notes-327.html]). You can download the latest version of Confluence Data Center from the download center ([https://www.atlassian.com/software/confluence/download-archives]). This vulnerability was discovered by m1sn0w and 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

CVE-2023-22526 is an authenticated remote code execution vulnerability in Atlassian Confluence Data Center and Server introduced in version 7.19.0. An authenticated attacker can execute arbitrary code with high impact to confidentiality, integrity, and availability, requiring no user interaction.

MitigationUpgrade Confluence Data Center/Server to version 7.19.17+, 8.5.5+, or 8.7.2+ (or any higher corresponding release) to remediate this RCE vulnerability.

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.17>= 8.5.0, < 8.5.5>= 8.7.0, < 8.7.2
Confluence ServerApplication
Affected:>= 7.19, < 7.19.17>= 8.5.0, < 8.5.5>= 8.7.0, <= 8.7.2

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
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 checks

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

  1. Identify Confluence version
    Access the Confluence web interface and navigate to the About page (typically /about/confluence) or check the confluence.version file in the Confluence installation directory
    Affected if The displayed version falls within any of these ranges: 7.19.0 through 7.19.16, 8.5.0 through 8.5.4, or 8.7.0 through 8.7.1 (for Data Center); 7.19.0 through 7.19.16, 8.5.0 through 8.5.4, or 8.7.0 through 8.7.2 (for Server)
  2. Confirm deployment type
    Check the Confluence administration console or license information to determine if the instance is Data Center or Server. The affected version ranges differ slightly between these deployment types
    Affected if The deployment is Confluence Data Center or Server with a version in the affected ranges listed above
  3. Verify authentication is enabled
    Confirm that user authentication is configured and functional. This vulnerability requires an authenticated attacker, so check that local user accounts, LDAP integration, or SSO are active in the Confluence user management settings
    Affected if Authentication is enabled and user accounts exist, allowing an attacker to obtain valid credentials and exploit the vulnerability
  4. Check network exposure
    Review whether the Confluence instance is accessible from external networks or the internet. Inspect firewall rules, reverse proxy configuration, or VPN settings that control access to the Confluence web interface
    Affected if The instance is exposed to untrusted networks where attackers could potentially obtain or use stolen credentials to reach Confluence

If Confluence Data Center or Server is running version 7.19.0-7.19.16, 8.5.0-8.5.4, or 8.7.0-8.7.1 (Data Center) or 8.7.2 (Server), and the instance is accessible to authenticated users, the environment is affected by this RCE vulnerability

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 7.19.17 / 8.5.5 / 8.7.2 or later
Fixed in 7.19.178.5.58.7.2
Interim mitigation

Upgrade Confluence Data Center/Server to version 7.19.17+, 8.5.5+, or 8.7.2+ (or any higher corresponding release) to remediate this RCE vulnerability.

Recommended fix High confidence

7.19.17+ or 8.5.5+ or 8.7.2+ (depending on your current major.minor version)

  1. 1. Identify the current Confluence version by navigating to Confluence Admin > General Configuration > Confluence Information
  2. 2. Create a complete backup of the Confluence database and home directory
  3. 3. Download the appropriate fixed version from Atlassian's download center (https://www.atlassian.com/software/confluence/download-archives)
  4. 4. If running Confluence 7.19.x: upgrade to 7.19.17 or later
  5. 5. If running Confluence 8.5.x: upgrade to 8.5.5 or later
  6. 6. If running Confluence 8.7.x: upgrade to 8.7.2 or later
  7. 7. Follow Atlassian's standard upgrade documentation for your deployment type (Data Center or Server)
  8. 8. Restart Confluence after the upgrade completes
Caveat Review Atlassian's upgrade notes for your target version as minor version upgrades may include configuration or compatibility changes

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-22526 — 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-2023-22526 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