CVE-2023-22515

CRITICALNVD 9.810.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 10.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-10-05), indicating real-world exploitation has been confirmed by US federal agencies. It is also listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD). NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild

Also known asEUVD-2023-26655 (ENISA EUVD) · GHSA-g458-xvmc-qg2r (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low mission impact
CISA-KEV: ExploitedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 99%CVSS: 9.8Exploit: Metasploit · other public PoCExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
9.8
EG Score
10.0CRITICALhigh confidence
EG Risk
100
EG Risk 100/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low mission impact; Act at medium or high.
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.
EPSS PROB
99%
EPSS %ILE
99th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
99% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and ENISA EU KEV (Source: ENISA EUVD) and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Act at medium mission impactAttend at low mission impact; Act at medium or high.CISA BOD 26-04: 3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed January 23, 2025, reported by cnw.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Attend at low mission impact; Act at medium or high.

No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation sooner than your normal schedule at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 3 days & forensic triage if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: this CVE is in CISA's KEV catalog, and CISA's required action for it, quoted below, applies whether or not a fix is released.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“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.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://confluence.atlassian.com/security/cve-2023-22515-privilege-escalation-vulnerability-in-confluence-data-center-and-server-1295682276.html · https://nvd.nist.gov/vuln/detail/CVE-2023-22515

Published

October 4, 2023

Last Modified

March 25, 2026

Advisory Details (5)

Auto-updated Oct 30, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). No fix on record yet. Sources: cisa.
CISA🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-22515
Web page

CVE-2023-22515 - Broken Access Control Vulnerability in Confluence Data Center and Server | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/pages/viewpage.action?pageId=1295682276
Web page

FAQ for CVE-2023-22515 | Atlassian knowledge base | Atlassian Support

https://confluence.atlassian.com/display/KB/FAQ+for+CVE-2023-22515

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 107× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 900 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 800 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 18:36 UTCEG score recompute
  2. 2026-11-01 18:36 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-10-31 17:56 UTCEG score recompute
  4. 2026-10-31 17:55 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-10-31 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  6. 2026-10-30 17:14 UTCEG score recompute
  7. 2026-10-30 17:14 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  8. 2026-10-29 16:34 UTCEG score recompute
  9. 2026-10-29 16:34 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  10. 2026-10-28 15:53 UTCEG score recompute
  11. 2026-10-28 15:53 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-10-27 15:12 UTCEG score recompute
  13. 2026-10-27 15:12 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  14. 2026-10-26 14:28 UTCEG score recompute
  15. 2026-10-26 14:28 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  16. 2026-10-25 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  17. 2026-10-25 13:47 UTCEG score recompute
  18. 2026-10-25 13:47 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  19. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2023-26655 · listed January 23, 2025 · reported by cnw · Source: ENISA EUVD
  20. 2026-10-24 20:36 UTCEG score recompute
  21. 2026-10-24 20:36 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  22. 2026-10-23 19:56 UTCEG score recompute
  23. 2026-10-23 19:56 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  24. 2026-10-22 19:15 UTCEG score recompute
  25. 2026-10-22 19:14 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
Show 75 more
  1. 2026-10-21 18:34 UTCEG score recompute
  2. 2026-10-21 18:34 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  3. 2026-10-21 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  4. 2026-10-20 17:53 UTCEG score recompute
  5. 2026-10-20 17:52 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-10-20 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  7. 2026-10-19 17:10 UTCEG score recompute
  8. 2026-10-19 17:10 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  9. 2026-10-19 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  10. 2026-10-18 16:27 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  11. 2026-10-18 13:29 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  12. 2026-10-18 08:13 UTCEG score recompute
  13. 2026-10-17 12:48 UTCEG score recompute
  14. 2026-10-17 12:48 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  15. 2026-10-16 12:06 UTCEG score recompute
  16. 2026-10-16 12:06 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  17. 2026-10-15 11:25 UTCEG score recompute
  18. 2026-10-15 11:25 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  19. 2026-10-14 10:45 UTCEG score recompute
  20. 2026-10-14 10:44 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  21. 2026-10-13 16:29 UTCEPSS rescoreEPSS 99% · 99th percentile
  22. 2026-10-13 10:02 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  23. 2026-10-12 18:36 UTCEG score recompute
  24. 2026-10-12 09:20 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  25. 2026-10-12 04:58 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  26. 2026-10-12 00:39 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  27. 2026-10-11 20:21 UTCEG score recompute
  28. 2026-10-11 20:20 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  29. 2026-10-11 16:01 UTCEG score recompute
  30. 2026-10-11 16:00 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  31. 2026-10-11 11:41 UTCEG score recompute
  32. 2026-10-11 11:41 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  33. 2026-10-11 07:22 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  34. 2026-10-11 03:03 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  35. 2026-10-10 22:43 UTCEG score recompute
  36. 2026-10-10 22:43 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  37. 2026-10-10 19:57 UTCEPSS rescoreEPSS 99% · 99th percentile
  38. 2026-10-10 18:23 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  39. 2026-10-10 14:04 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  40. 2026-10-10 09:45 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  41. 2026-10-10 05:27 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  42. 2026-10-10 01:06 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  43. 2026-10-09 20:45 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  44. 2026-10-09 16:26 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  45. 2026-10-09 12:07 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  46. 2026-10-09 07:47 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  47. 2026-10-09 03:28 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  48. 2026-10-08 23:09 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  49. 2026-10-08 18:50 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  50. 2026-10-08 14:32 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  51. 2026-10-08 10:10 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  52. 2026-10-08 05:50 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  53. 2026-10-08 01:31 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  54. 2026-10-07 21:12 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  55. 2026-10-07 16:52 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  56. 2026-10-07 12:32 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  57. 2026-10-07 08:12 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  58. 2026-10-07 03:53 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  59. 2026-10-06 23:34 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  60. 2026-10-06 19:15 UTCEG score recompute
  61. 2026-10-06 19:15 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  62. 2026-10-06 15:14 UTCEPSS rescoreEPSS 99% · 99th percentile
  63. 2026-10-06 14:56 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  64. 2026-10-06 10:36 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  65. 2026-10-06 06:16 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  66. 2026-10-06 01:57 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  67. 2026-10-05 21:38 UTCEG score recompute
  68. 2026-10-05 21:38 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  69. 2026-10-05 17:40 UTCEPSS rescoreEPSS 99% · 99th percentile
  70. 2026-10-05 17:17 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  71. 2026-10-05 12:58 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  72. 2026-10-05 08:40 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  73. 2026-10-05 04:21 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  74. 2026-10-05 00:01 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0
  75. 2026-10-04 19:43 UTCGHSA enrichmentGHSA-g458-xvmc-qg2r · GitHub severity CRITICAL · GitHub CVSS 10.0

Publicly available exploits

(15 references, 10 shown)

Public exploit code is referenced for this CVE (2 Metasploit modules, 10 GitHub PoCs), as are 1 Nuclei detection template, 2 GitHub checker repositories. A detection template checks whether a system is affected; it is not necessarily exploit code. A GitHub repository named or described as a checker or scanner checks whether a system is affected; it is not necessarily exploit code. No fix is confirmed yet, so defenders should restrict or isolate affected systems accordingly until one is published.

  • Metasploitauxiliary/admin/http/atlassian_confluence_auth_bypass✓ verified
    Published Oct 19, 2023

    Atlassian Confluence Data Center and Server Authentication Bypass via Broken Access Control

    Open source ↗
  • Metasploitexploit/multi/http/atlassian_confluence_rce_cve_2023_22515✓ verified
    Published Oct 19, 2023

    Atlassian Confluence Unauthenticated Remote Code Execution

    Open source ↗
  • GitHub checkerspareack/CVE-2023-22515-NSE
    Published Jul 18, 2024

    Vulnerability checking tool via Nmap Scripting Engine

    Open source ↗
  • GitHub PoCaaaademo/Confluence-EvilJar
    Published Nov 9, 2023

    配合 CVE-2023-22515 后台上传jar包实现RCE

    Open source ↗
  • GitHub PoCAIex-3/confluence-hack
    Published Oct 30, 2023

    CVE-2023-22515

    Open source ↗
  • GitHub PoCyoucannotseemeagain/CVE-2023-22515_RCE
    Published Oct 20, 2023

    Confluence后台rce

    Open source ↗
  • GitHub PoCLe1a/CVE-2023-22515
    Published Oct 13, 2023

    Confluence Data Center & Server 权限提升漏洞 Exploit

    Open source ↗
  • GitHub PoCK4ptor/CVE-2023-22515
    Published Oct 12, 2023

    Confluence Unauthorized Administrator User Addition Exploitation Script

    Open source ↗
  • GitHub PoCs1incere/CVE-2023-22515
    Published Oct 12, 2023

    Confluence Unauthorized Administrator User Addition Exploitation Script

    Open source ↗
  • GitHub PoCad-calcium/CVE-2023-22515
    Published Oct 11, 2023

    Confluence未授权添加管理员用户(CVE-2023-22515)漏洞利用工具

    Open source ↗

Frequently asked(6)

What is CVE-2023-22515?
CVE-2023-22515 is a critical-severity vulnerability; its CVE record was published on October 4, 2023. 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…
When was the CVE record for CVE-2023-22515 published?
The CVE record for CVE-2023-22515 was published on October 4, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of March 25, 2026; the record at its source may have been updated since.
Is CVE-2023-22515 actively exploited?
Yes. CISA added CVE-2023-22515 to the Known Exploited Vulnerabilities catalog on October 5, 2023, affecting Atlassian Confluence Data Center and Server. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. No fix is confirmed yet. Check the vendor's advisory for a fixed release; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2023-22515 (added January 23, 2025, reported by cnw): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement.
What is the CVSS score of CVE-2023-22515?
CVE-2023-22515 has a CVSS v3 base score of 9.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + ENISA's EU KEV (Source: ENISA EUVD) + FIRST EPSS + GHSA into a combined EG score of 10.0 (CRITICAL).
Which products are affected by CVE-2023-22515?
CVE-2023-22515 affects Atlassian Confluence Data Center and Server.
How do I remediate CVE-2023-22515?
No fix for CVE-2023-22515 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-22515

Explore →

Is Your Infrastructure Affected by CVE-2023-22515?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.