dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-52840

MEDIUM · 5.4 CVSS v3.1 Published 2024-12-10
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 by an attacker to execute arbitrary code in the context of the victim's browser session. By manipulating a DOM element through a crafted URL or user input, the attacker can inject malicious scripts that run when the page is rendered. This type of attack requires user interaction, as the victim would need to access the manipulated URL or input the malicious data themselves.

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.21 and earlier contain a DOM-based XSS vulnerability where attackers can inject malicious scripts through crafted URLs or user input that manipulate DOM elements, causing script execution when pages render.

MitigationUpdate to AEM 6.5.22 or later; implement input validation and output encoding for user-supplied data in DOM manipulations, and deploy Content Security Policy headers to mitigate 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.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. Verify AEM product version
    Access the AEM Web Console (\u003c host\u003e:/system/console/status-versions) or check the crx-quickstart/launcher.properties file to identify the installed AEM version
    Affected if The installed version is lower than 6.5.22.0 or lower than 2024.11.0
  2. Identify custom components accepting user input
    Review the codebase for custom AEM components, sightly templates, or HTL files that accept and render user-supplied parameters or request attributes without validation
    Affected if Custom components pass user input directly to DOM manipulation functions without sanitization
  3. Examine JavaScript for unsafe DOM operations
    Search custom clientlibs or inline scripts for functions like innerHTML, insertAdjacentHTML, document.write, or eval that process URL parameters or user data without proper encoding
    Affected if The codebase contains DOM manipulation code that uses untrusted input without output encoding
  4. Check for absence of input validation patterns
    Review custom code for the absence of XSS prevention measures such as input validation, output encoding (using encoder libraries), or CSP enforcement in custom components
    Affected if Custom components lack input validation and output encoding when handling user-controlled data in DOM operations

The environment is affected if the installed AEM version is below 6.5.22.0 or below 2024.11.0 and custom code or components handle user input in DOM manipulation without proper sanitization.

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

Update to AEM 6.5.22 or later; implement input validation and output encoding for user-supplied data in DOM manipulations, and deploy Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

6.5.22.0 (for 6.5.x line) or 2024.11.0+ (for Cloud Service)

  1. 1. Identify your current Adobe Experience Manager version in the AEM Web Console (Navigate to Help > Version)
  2. 2. For AEM 6.5.x on-premises: Plan upgrade to version 6.5.22.0 or later
  3. 3. For AEM as a Cloud Service: Plan upgrade to 2024.11.0 or later version
  4. 4. Review Adobe's upgrade documentation for your deployment type (helpx.adobe.com)
  5. 5. Create a backup of your current AEM instance and content repository
  6. 6. Test the upgrade in a staging environment before production deployment
  7. 7. Execute the upgrade following Adobe's recommended upgrade procedure
  8. 8. Verify the XSS vulnerability is remediated by testing the previously vulnerable URL patterns
Caveat Point releases (6.5.21 to 6.5.22) typically have minimal breaking changes; however, test custom code and integrations in staging before production upgrade

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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