dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26039

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 Answer: 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 requires user interaction, such as convincing a victim to click on a specially crafted link or to submit a form that triggers the vulnerability.

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 malicious JavaScript can be injected through the DOM manipulation of user-supplied input. This allows attackers to execute arbitrary JavaScript in the victim's browser context when they interact with specially crafted links or forms.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the patch. Implement Content Security Policy (CSP) headers and validate/sanitize all user inputs on the client side to prevent DOM-based XSS execution.

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. Check Adobe Experience Manager version
    Access the AEM system console at /system/console/product.json or view the version from the AEM Welcome page (select Tools > Operations > Web Console, then look at the Product Information section)
    Affected if The installed version is 6.5.20 or earlier, or falls below version 2024.5
  2. Identify the exact product version number
    In the AEM Web Console, navigate to the Product Information page or check the crx-quickstart/conf folder for version.info file
    Affected if The version displayed is lower than 6.5.21 or lower than 2024.5
  3. Determine the release track
    Check whether the installation follows the 6.5.x LTS track or the newer 2024.x rapid release track by reviewing the version number format in the product info
    Affected if Running on 6.5.x track below 6.5.21, or on 2024.x track below 2024.5

You are affected if your AEM installation is version 6.5.20 or earlier on the 6.5.x LTS track, or any version below 2024.5 on the 2024.x release track.

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

Upgrade Adobe Experience Manager to version 6.5.21 or later to obtain the patch. Implement Content Security Policy (CSP) headers and validate/sanitize all user inputs on the client side to prevent DOM-based XSS execution.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x line) or AEM 2024.5 (for 2024.x line)

  1. 1. Identify the current Adobe Experience Manager version in your environment
  2. 2. Determine which release line you are on (6.5.x legacy line or 2024.x newer line)
  3. 3. If on the 6.5.x line: download and plan upgrade to AEM 6.5.21 or later
  4. 4. If on the 2024.x line: download and plan upgrade to AEM 2024.5 or later
  5. 5. Backup your current AEM instance and content repositories before upgrading
  6. 6. Test the upgrade in a staging or development environment first
  7. 7. Validate that custom code and integrations work correctly after upgrade
  8. 8. Deploy the upgraded version to production
Caveat Standard upgrade risks apply; test thoroughly in non-production first

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-26039 — 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-26039 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