dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-53967

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-19
Fix available
A fix is available. Upgrade to 6.5.22.0 / 2024.11.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Experience Manager versions 6.5.21 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be exploited to execute arbitrary code in the context of the victim's browser session. By manipulating the DOM environment in the victim's browser, a low privileged attacker can inject malicious scripts that are executed by the victim's browser. Exploitation of this issue requires user interaction, typically in the form of following a malicious link.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Adobe Experience Manager versions 6.5.21 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where client-side JavaScript improperly handles user-controlled input in the DOM, allowing a low-privileged attacker to inject malicious scripts via a crafted link that the victim clicks.

MitigationApply the vendor patch from Adobe for AEM 6.5.21 and earlier. Until patched, users should avoid clicking untrusted links. Organizations should also implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Experience ManagerApplication
Affected:< 6.5.22.0< 2024.11.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed AEM version
    Access the AEM Welcome page or system console (/libs/granite/ui/content/shell/overview.html) and locate the version information typically displayed in the 'Version' field of the AEM product. Alternatively, check the manifest file in the installation directory or the content of the 'version.properties' file found in the crx-quickstart folder.
    Affected if The displayed version is earlier than 6.5.22.0 or earlier than 2024.11.0 (for cloud/2024 releases).
  2. Verify AEM 6.5.x release version
    For AEM 6.5 installations, run the AEM version check via thefelix gateway or inspect the productinfo endpoint if accessible in your environment.
    Affected if Running version check returns a build version below 6.5.22.0.
  3. Confirm if unauthenticated or low-privileged user access is possible
    Verify that the AEM instance allows access to content pages or user-generated content areas where a crafted link could be presented to a victim. DOM-based XSS requires a user to interact with a malicious link.
    Affected if The instance exposes web content pages to users who can click externally-supplied links without additional security filtering.

A user is affected if their AEM installation version is below 6.5.22.0 (6.5.x line) or below 2024.11.0 (2024 release line) and the application serves web content to users who could click a crafted link.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 6.5.22.0 / 2024.11.0 or later
Fixed in 6.5.22.02024.11.0
Interim mitigation

Apply the vendor patch from Adobe for AEM 6.5.21 and earlier. Until patched, users should avoid clicking untrusted links. Organizations should also implement Content Security Policy (CSP) headers as a defense-in-depth measure.

Recommended fix High confidence

AEM 6.5.22.0 (for 6.5.x branches) or AEM 2024.11.0 (for 2024.x branches)

  1. 1. Identify your current Adobe Experience Manager version by checking the product welcome page or system console.
  2. 2. Determine your release branch: if running AEM 6.5.x, plan upgrade to 6.5.22.0; if running AEM 2024.x, plan upgrade to 2024.11.0.
  3. 3. Review Adobe's official upgrade documentation for your specific version path.
  4. 4. Perform a full backup of your AEM instance, including repository, database, and configuration files.
  5. 5. Test the upgrade in a non-production environment first to verify compatibility with custom code and configurations.
  6. 6. Schedule a maintenance window and execute the production upgrade.
  7. 7. After upgrade, verify the AEM version reflects the fixed release (6.5.22.0 or 2024.11.0).
  8. 8. Test that the DOM-based XSS vulnerability is no longer exploitable by validating that user-supplied input is properly escaped in the affected components.
Caveat Standard AEM upgrade considerations apply: review deprecated APIs, test custom bundles and workflows, verify third-party integrations, and update any dependencies that may not be compatible with the new version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-53967 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data