dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26072

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 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.20 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser session. Exploitation of this issue typically requires user interaction, such as convincing a victim to click on a specially crafted link or to submit a form that causes the vulnerable script to execute.

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.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where client-side JavaScript processes user input from the DOM without proper sanitization. An attacker can craft malicious links or forms that cause arbitrary JavaScript execution in the victim's browser session when interacted with.

MitigationApply Adobe's security patch (upgrade to AEM 6.5.21 or later) and validate that all user-supplied data in JavaScript code paths uses proper output encoding or content security policy headers.

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.21< 2024.5

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. Determine AEM version
    Navigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/product.json to retrieve the exact installed version number
    Affected if Version shows 6.5.20 or earlier, or a version below the 2024.5 milestone
  2. Check AEM package version via console
    Access /system/console/bundles and locate the core AEM bundles, or run 'npm version' if using AEM as a Cloud Service SDK, to confirm the specific release build number
    Affected if Bundle version is prior to the 6.5.21 release or the 2024.5 release
  3. Identify custom client-side code paths
    Review /apps and /libs directories for custom JavaScript files (js.jsp, js.html, .js files) that read parameters from the DOM using location.search, document.referrer, or similar client-side APIs
    Affected if Custom JavaScript directly embeds URL parameters or DOM elements into HTML without encoding
  4. Audit content security policy headers
    Use browser developer tools Network tab to inspect response headers from AEM pages, or check the Apache Sling header configuration in /system/console/config for Content-Security-Policy directives
    Affected if CSP headers are missing, weak, or allow unsafe-inline scripts

You are affected if your AEM installation is version 6.5.20 or earlier (or pre-2024.5 for cloud), or if custom client-side code processes DOM input unsafely without CSP mitigation.

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.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Apply Adobe's security patch (upgrade to AEM 6.5.21 or later) and validate that all user-supplied data in JavaScript code paths uses proper output encoding or content security policy headers.

Recommended fix High confidence

AEM 6.5.21 (on-premise) or AEM Cloud Service 2024.5

  1. 1. Back up your current Adobe Experience Manager instance and database before proceeding with any upgrade.
  2. 2. Review the Adobe Experience Manager upgrade documentation for your deployment type (on-premise or cloud service).
  3. 3. For on-premise (6.x) installations: Upgrade to Adobe Experience Manager 6.5.21 by following the standard upgrade procedures in the official documentation.
  4. 4. For cloud service (2024.x) deployments: Upgrade to the 2024.5 release through the Adobe Cloud Manager or by requesting the upgrade from Adobe.
  5. 5. After upgrading, verify that the AEM instance starts successfully and all custom code remains functional.
  6. 6. Test the specific functionality that was vulnerable to ensure the XSS fix is properly applied.
Caveat Review the AEM 6.5.21 release notes for any compatibility notices or deprecated features before upgrading

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26072 — 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-26072 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