Confluence Data CenterApplication · Atlassian
CVE-2023-22503
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 anonymous remote attackers to view the names of attachments and labels in a private Confluence space. This occurs via an Information Disclosure vulnerability in the macro preview feature. This vulnerability was reported by Rojan Rijal of the Tinder Security Engineering team. The affected versions are before version 7.13.15, from version 7.14.0 before 7.19.7, and from version 7.20.0 before 8.2.0.
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 confidenceThis is an information disclosure vulnerability in Atlassian Confluence Server and Data Center's macro preview feature. Anonymous remote attackers can bypass access controls and view the names of attachments and labels within private Confluence spaces they are not authorized to access.
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.13.15>= 7.14.0, < 7.19.7>= 7.20.0, < 8.2.0
Confluence ServerApplication
< 7.13.15>= 7.14.0, < 7.19.7>= 7.20.0, < 8.2.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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.
-
Determine Confluence installation versionLog in as an administrator and navigate to the Confluence Administration console, then go to General Configuration or About to find the installed version number. Alternatively, access the /about endpoint or check the confluence.cfg.xml configuration file for the version entry.Affected if The installed version falls within any of these vulnerable ranges: < 7.13.15; >= 7.14.0 and < 7.19.7; >= 7.20.0 and < 8.2.0
-
Verify if anonymous access is enabledIn the Confluence Administration console, go to Security Configuration or User Management settings and check whether anonymous access is permitted. This can also be verified by attempting to access Confluence without providing credentials.Affected if Anonymous access is enabled and the Confluence version is vulnerable according to the ranges above
-
Confirm the macro preview feature is accessibleAttempt to access the macro preview functionality on a page within a private space while operating as an anonymous user. The vulnerability exploits the macro preview feature to leak attachment and label names from restricted spaces.Affected if An unauthenticated user can retrieve names of attachments or labels from private spaces that they are not authorized to view
A Confluence instance is affected if it runs a vulnerable version (less than 7.13.15, between 7.14.0-7.19.6, or between 7.20.0-8.1.x) AND anonymous access is enabled, allowing unauthorized disclosure of attachment and label names from private spaces.
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 · scoped7.13.157.19.78.2.0
Upgrade Confluence to version 7.13.15, 7.19.7, 8.2.0 or later to patch the vulnerability. If immediate patching is not feasible, disable or restrict anonymous access to Confluence instances as a compensating control.
Confluence Server/Data Center 8.2.0 or later (or 7.19.7 for 7.x branch)
- 1. Back up your Confluence database and installation directory before proceeding with any upgrade.
- 2. Review Atlassian's upgrade guide and release notes for the target version to understand any migration requirements.
- 3. Download Confluence Server or Data Center version 8.2.0 or later from the Atlassian downloads page.
- 4. If upgrading from a major version earlier than 8.0, review and address any pre-upgrade requirements documented by Atlassian.
- 5. Stop the Confluence service.
- 6. Install the new version following Atlassian's standard upgrade procedure.
- 7. Start the Confluence service and verify the application is functioning correctly.
- 8. Confirm the vulnerability is remediated by testing that anonymous users can no longer view attachment or label names in private spaces.
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
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-22503 — 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-2023-22503 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