CVE REMEDIATION GUIDE
CISA KEV · Known exploitedCriticalFixed-version data available

CVE-2023-22518 remediation guide

Atlassian Confluence Data Center and Server

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 dom...

Open CVE record
ProductAtlassian Confluence Data Center and Server
Affected versions>= 1.0.0, >= 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
Fixed versions7.19.16, 8.3.4, 8.4.4, 8.5.3
Priority basisImmediate · CVSS 9.8 · EPSS 100.0%
01

Identify the affected asset

Confirm whether Atlassian Confluence Data Center and Server is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= 1.0.0, >= 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. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

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

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.

CVE-2023-22518 Remediation Guide | SECUFOCUS NOW