CVE-2023-22515 Atlassian Confluence Data Center and Server Broken Access Control Vulnerability
Atlassian Confluence Data Center and Server contains a broken access control vulnerability that allows an attacker to create unauthorized Confluence administrator accounts and access Confluence.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 5 Oct 2023.
- CISA lists it as known to be used in ransomware campaigns.
- Rated Critical severity (CVSS 10.0, scored by Vendor).
- This product type is often exposed to the internet, which is where attackers scan for it first.
- It has been in the catalogue for 1,128 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
Atlassian has been made aware of an issue reported by a handful of customers where external attackers may have exploited a previously unknown vulnerability in publicly accessible Confluence Data Center and Server instances to create unauthorized Confluence administrator accounts and access Confluence instances. Atlassian Cloud sites are not affected by this vulnerability. If your Confluence site is accessed via an atlassian.net domain, it is hosted by Atlassian and is not vulnerable to this issue.
Affected Versions
| Product | Versions |
|---|---|
| Atlassian Confluence Data Center | >= 8.0.0 >= 8.0.1 >= 8.0.2 >= 8.0.3 >= 8.1.3 |
| Atlassian Confluence Server | >= 8.0.0 >= 8.0.1 >= 8.0.2 >= 8.0.3 >= 8.1.3 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Atlassian Confluence Data Center and Server. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Check all affected Confluence instances for evidence of compromise per vendor instructions and report any positive findings to CISA.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2023-22515 and every other exploited flaw on the list.
Sources
- CISA Known Exploited Vulnerabilities catalogue
- NVD: CVE-2023-22515
- CVE record: CVE-2023-22515
- FIRST EPSS
- confluence.atlassian.com/security/cve-2023-22515-privilege-escalation-vulnerability-in-confluence-da
- packetstormsecurity.com/files/175225/Atlassian-Confluence-Unauthenticated-Remote-Code-Execution.html
- confluence.atlassian.com/display/KB/FAQ+for+CVE-2023-22515
- confluence.atlassian.com/pages/viewpage.action?pageId=1295682276
- jira.atlassian.com/browse/CONFSERVER-92475
