SecOps SignalSecurity Intelligence Workspace
Loading collection status
Vulnerabilities/CVE-2023-22518Public Intelligence Dossier
Source: atlassian · Limited verification•Last verified: •Collection Degraded
CVE-2023-22518ListedCRITICAL (raw)CVSS 10.0CWE-863

All versions of Confluence Data Center and Server are affected by this unexploited vulnerability

Published: 31 Oct 2023•Last updated: 17 Jun 2026, 11:05 AM IST•Source identifier: security@atlassian.com
Dossier completeness: source-provided sections 3 / 3 · rule guidance available. Missing source facts count as incomplete.
Official source
CISA KEV catalog
Listed
Added07 Nov 2023
Due28 Nov 2023
RansomwareKnown
CVSS score
10.0CRITICAL (raw)
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Metric sourcesecurity@atlassian.com
EPSS probability
100%1.000
Percentile100th
Weakness type
CWE-863
No further CWE recorded
Remediation
Patch status unknown
No fixed version or KB recorded

Why It Matters

Analysis dossier

Why It Matters

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.

SOC priority

Immediate Attention

Actively exploited (source statement)

Yes

Publicly disclosed

Unknown

Risk basis: CISA KEV exploitation signal; SOC ecosystem technology relevance; CRITICAL severity; Known exploitation signal from CISA KEV or ransomware metadata

Affected Products & Remediation

2 source-backed products
Affected products and versions (source)
  • atlassian confluence data center · >= 1.0 < 7.19.16; >= 7.20.0 < 8.3.4; >= 8.4.0 < 8.4.4; >= 8.5.0 < 8.5.3; 8.6.0 · NVD CPE · Source
  • atlassian confluence server · >= 1.0 < 7.19.16; >= 7.20.0 < 8.3.4; >= 8.4.0 < 8.4.4; >= 8.5.0 < 8.5.3; 8.6.0 · NVD CPE · Source
Recorded patch / KBNot provided by source

Vendor or catalog guidance (source)

  • CISA KEV: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Known exploitation (source facts)

Only what a source states. Unknown means no source has said either way; it is not "not exploited".

CISA KEV
Listed
Exploited (source statement)
Yes
Publicly disclosed (source)
Unknown

CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Suggested hunting (rule-based inference)

SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.

Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); authorization-bypass (CWE-863)

Exposure

  1. Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
  2. Locate affected authorization controls and verify deployed versions.Telemetry: Application inventory · The source must identify the affected control. · Rule authorization-bypass

Exploitation evidence

  1. Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)

Exploitation evidence

  1. Review privileged operations performed by unexpected users on affected deployments.Telemetry: Application audit logs · Authorization anomalies can support a targeted hunt. · Rule authorization-bypass

Response

  1. Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure

CISA KEV Record

Catalog entry
07 Nov 2023
Required action due
28 Nov 2023
Known ransomware use
Known

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Change History & Source Data

— No recorded material change

CNA / source
security@atlassian.com
Record status · verification
UPDATED · CISA KEV confirmed
CPE
cpe:2.3:a:atlassian:confluence_data_center:*:*:*:*:*:*:*:*, cpe:2.3:a:atlassian:confluence_data_center:8.6.0:*:*:*:*:*:*:*, cpe:2.3:a:atlassian:confluence_server:*:*:*:*:*:*:*:*, cpe:2.3:a:atlassian:confluence_server:8.6.0:*:*:*:*:*:*:*

Linked by the query's stored exact CVE association. Review required tables and validation status before use.

Detection Hunting Query
Target: DeviceTvmSoftwareVulnerabilities•Defender XDR
Detect endpoints exposed to CVE-2023-22518
Purpose: Exposure assessment (Category: Exposure Check)Why linked: Query metadata names CVE-2023-22518
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2023-22518"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc
Schema Checked · Not runtime validatedSource: SecOps Signal deterministic template · Limited verificationStatic screening: Passed structure and schema checks; tenant execution is not verified.
Loading related intelligence

Correlated briefings

SecOps Signal surfaces public advisory facts only. A missing value means the source has not published it, not that your environment is unaffected. No tenant inventory is connected.