CVE-2023-22518

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score elevated to 9.8 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-11-07), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 9.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Exploited in the wild

Also known asEUVD-2023-26658 (ENISA EUVD) · GHSA-8prx-84h6-4fr5 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
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 or medium mission impact
CISA-KEV: ExploitedEPSS PROB: >99.9%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.

All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. This Improper Authorization vulnerability allows an unauthenticated attacker to reset Confluence and create a Confluence instance administrator account. Using this account, an attacker can then perform all administrative actions that are available to Confluence instance administrator leading to - but not limited to - full loss of confidentiality, integrity and availability. 

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
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 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 or medium mission impact; Act at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 or medium mission impact and as soon as possible at high.
EPSS PROB
>99.9%
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
>99.9% 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 EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactAttend at low or medium mission impact; Act at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 14 days 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.

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

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 or medium mission impact and as soon as possible at high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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 if the affected system is publicly exposed; 14 days 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 partial (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.”

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-22518-improper-authorization-vulnerability-in-confluence-data-center-and-server-1311473907.html · https://nvd.nist.gov/vuln/detail/CVE-2023-22518

Published

October 31, 2023

Last Modified

October 24, 2025

Advisory Details (4)

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-22518
Web page

CVE-2023-22518 - Improper Authorization Vulnerability In Confluence Data Center and Server | Atlassian Support | Atlassian Documentation

https://confluence.atlassian.com/pages/viewpage.action?pageId=1311473907

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 99× 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 967 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 867 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 22:40 UTCEG score recompute
  2. 2026-11-01 22:40 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-31 20:21 UTCEG score recompute
  4. 2026-10-31 20:21 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  5. 2026-10-30 18:02 UTCEG score recompute
  6. 2026-10-30 18:02 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  7. 2026-10-29 15:44 UTCEG score recompute
  8. 2026-10-29 15:43 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  9. 2026-10-28 13:25 UTCEG score recompute
  10. 2026-10-28 13:24 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  11. 2026-10-27 11:05 UTCEG score recompute
  12. 2026-10-27 11:05 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-26 08:47 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  14. 2026-10-25 17:49 UTCEG score recompute
  15. 2026-10-25 06:28 UTCEG score recompute
  16. 2026-10-25 06:27 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-24 04:08 UTCEG score recompute
  18. 2026-10-24 04:08 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  19. 2026-10-23 01:47 UTCEG score recompute
  20. 2026-10-23 01:47 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  21. 2026-10-21 23:27 UTCEG score recompute
  22. 2026-10-21 23:27 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-20 21:05 UTCEG score recompute
  24. 2026-10-20 21:05 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-19 18:46 UTCEG score recompute
Show 75 more
  1. 2026-10-19 18:46 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  2. 2026-10-18 16:26 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  3. 2026-10-18 08:13 UTCEG score recompute
  4. 2026-10-17 17:21 UTCEG score recompute
  5. 2026-10-17 17:21 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  6. 2026-10-16 15:01 UTCEG score recompute
  7. 2026-10-16 15:01 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  8. 2026-10-15 12:42 UTCEG score recompute
  9. 2026-10-15 12:41 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  10. 2026-10-14 10:20 UTCEG score recompute
  11. 2026-10-14 10:20 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  12. 2026-10-13 07:58 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  13. 2026-10-12 18:36 UTCEG score recompute
  14. 2026-10-12 05:39 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  15. 2026-10-12 01:55 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  16. 2026-10-11 22:14 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  17. 2026-10-11 21:59 UTCEG score recompute
  18. 2026-10-11 18:34 UTCEG score recompute
  19. 2026-10-11 18:34 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  20. 2026-10-11 14:53 UTCEG score recompute
  21. 2026-10-11 14:53 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  22. 2026-10-11 11:11 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  23. 2026-10-11 07:30 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  24. 2026-10-11 03:50 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  25. 2026-10-11 00:09 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  26. 2026-10-10 20:29 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  27. 2026-10-10 16:48 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  28. 2026-10-10 13:06 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  29. 2026-10-10 09:25 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  30. 2026-10-10 05:45 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  31. 2026-10-10 02:05 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  32. 2026-10-09 22:24 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  33. 2026-10-09 18:44 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  34. 2026-10-09 15:04 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  35. 2026-10-09 11:24 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  36. 2026-10-09 07:44 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  37. 2026-10-09 04:03 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  38. 2026-10-09 00:22 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  39. 2026-10-08 20:42 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  40. 2026-10-08 17:02 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  41. 2026-10-08 13:21 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  42. 2026-10-08 09:38 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  43. 2026-10-08 05:58 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  44. 2026-10-08 02:18 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  45. 2026-10-07 22:37 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  46. 2026-10-07 18:57 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  47. 2026-10-07 15:17 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  48. 2026-10-07 11:37 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  49. 2026-10-07 07:57 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  50. 2026-10-07 04:17 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  51. 2026-10-07 00:36 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  52. 2026-10-06 20:53 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  53. 2026-10-06 17:11 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  54. 2026-10-06 13:31 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  55. 2026-10-06 09:50 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  56. 2026-10-06 06:10 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  57. 2026-10-06 06:06 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  58. 2026-10-06 02:22 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  59. 2026-10-05 22:41 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  60. 2026-10-05 19:01 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  61. 2026-10-05 15:21 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  62. 2026-10-05 11:39 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  63. 2026-10-05 08:00 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  64. 2026-10-05 04:20 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  65. 2026-10-05 00:39 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  66. 2026-10-04 20:59 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  67. 2026-10-04 17:19 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  68. 2026-10-04 13:38 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  69. 2026-10-04 09:58 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  70. 2026-10-04 06:17 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  71. 2026-10-04 02:37 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  72. 2026-10-03 22:57 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  73. 2026-10-03 19:17 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  74. 2026-10-03 15:37 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1
  75. 2026-10-03 11:56 UTCGHSA enrichmentGHSA-8prx-84h6-4fr5 · GitHub severity CRITICAL · GitHub CVSS 9.1

Publicly available exploits

(6 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 3 GitHub PoCs), as are 1 Nuclei detection template, 1 GitHub checker repository. 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.

  • Metasploitexploit/multi/http/atlassian_confluence_unauth_backup✓ verified
    Published Dec 18, 2023

    Atlassian Confluence Unauth JSON setup-restore Improper Authorization leading to RCE (CVE-2023-22518)

    Open source ↗
  • GitHub PoC0x0d3ad/CVE-2023-22518
    Published Nov 9, 2023

    Exploit CVE-2023-22518

    Open source ↗
  • GitHub PoCRevoltSecurities/CVE-2023-22518
    Published Nov 5, 2023

    An Exploitation tool to exploit the confluence server that are vulnerable to CVE-2023-22518 Improper Authorization

    Open source ↗
  • GitHub checkerdavidfortytwo/CVE-2023-22518
    Published Nov 2, 2023

    Checker for CVE-2023-22518 vulnerability on Confluence

    Open source ↗
  • Nucleihttp/cves/2023/CVE-2023-22518.yaml
    Published Nov 2, 2023

    Atlassian Confluence Server - Improper Authorization

    Open source ↗
  • GitHub PoCForceFledgling/CVE-2023-22518
    Published Oct 31, 2023

    Improper Authorization Vulnerability in Confluence Data Center and Server

    Open source ↗

Frequently asked(6)

What is CVE-2023-22518?
CVE-2023-22518 is a critical-severity vulnerability; its CVE record was published on October 31, 2023. All versions of Confluence Data Center and Server are affected by this unexploited vulnerability. This Improper Authorization vulnerability allows an unauthenticated attacker to reset Confluence and create a Confluence instance administrator account. Using this account, an attacker can then perform…
When was the CVE record for CVE-2023-22518 published?
The CVE record for CVE-2023-22518 was published on October 31, 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 October 24, 2025; the record at its source may have been updated since.
Is CVE-2023-22518 actively exploited?
Yes. CISA added CVE-2023-22518 to the Known Exploited Vulnerabilities catalog on November 7, 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.
What is the CVSS score of CVE-2023-22518?
CVE-2023-22518 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2023-22518?
CVE-2023-22518 affects Atlassian Confluence Data Center and Server.
How do I remediate CVE-2023-22518?
No fix for CVE-2023-22518 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-22518

Explore →

Is Your Infrastructure Affected by CVE-2023-22518?

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