dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36239

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.

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 · moderate confidence

Adobe Experience Manager versions 6.5.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability that allows attackers to execute arbitrary JavaScript code in the context of a victim's browser session through specially crafted links requiring user interaction.

MitigationUpgrade to Adobe Experience Manager version 6.5.21 or later. Users should be cautioned against clicking untrusted links to mitigate the user-interaction requirement for exploitation.

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. Confirm Adobe Experience Manager is deployed
    Identify AEM instances in your environment by checking for common AEM indicators such as the /libs/cq/core/content/welcome.html or /crx/packmgr endpoints, or by scanning for AEM-specific web artifacts.
    Affected if AEM is present in the environment
  2. Determine installed AEM version
    Access the AEM version information via the product.json endpoint (for example, /libs/cq/core/content/product.json) or by inspecting the JAR file manifest in the installation directory.
    Affected if The version cannot be determined or is not visible
  3. Compare version against affected ranges
    Check if the installed version is less than 6.5.21 or less than 2024.5. Note that AEM uses two versioning schemes: the 6.5.x line uses 6.5.x numbering, while cloud and newer releases use the year.month format.
    Affected if Installed version is below 6.5.21 or below 2024.5
  4. Assess user-facing exposure
    Evaluate whether end-users have access to interfaces where they could click on external or untrusted links, as exploitation requires user interaction with a specially crafted link.
    Affected if Users can interact with external links without filtering or warning mechanisms

AEM instances running versions below 6.5.21 or below 2024.5 are affected by this DOM-based XSS vulnerability and users clicking malicious links could have arbitrary JavaScript executed in their browser session.

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 to Adobe Experience Manager version 6.5.21 or later. Users should be cautioned against clicking untrusted links to mitigate the user-interaction requirement for exploitation.

Recommended fix High confidence

AEM 6.5.21 (or later for 6.5.x) / AEM as a Cloud Service 2024.5 (or later release)

  1. Review Adobe's official security bulletin on helpx.adobe.com for detailed upgrade instructions and prerequisites
  2. Plan the upgrade by scheduling a maintenance window and creating a full backup of the current AEM environment
  3. Upgrade Adobe Experience Manager 6.5.x installations to version 6.5.21 or later
  4. If using AEM as a Cloud Service, upgrade to the 2024.5 release or later release
  5. After upgrading, clear the AEM cache and rebuild any custom indexes if required
  6. Validate the fix by testing the previously vulnerable endpoint with the expected attack vector
  7. Monitor the system logs for any unusual JavaScript execution or XSS-related errors
Caveat Standard AEM minor version upgrades typically have minimal breaking changes, but review release notes and test in non-production environment before deploying to production

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 / QA3.0 h
19.0 hours of engineering $3,380
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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