CVE-2024-52860
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 · uneditedAdobe 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. User interaction is required for exploitation, as a victim must visit a malicious link or input data into a vulnerable web application.
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 confidenceAdobe Experience Manager versions 6.5.21 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability where malicious scripts can be injected through manipulated DOM elements via crafted URLs or user input, executing in the context of the victim's browser session when the page renders.
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< 6.5.22.0< 2024.11.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed AEM versionAccess the AEM Web Console by navigating to /system/console/configMgr or check the product.ini file in the crx-quickstart folder. Alternatively, run the command: java -jar cq-quickstart-*.jar -version or check the manifest file in core jars.Affected if The installed version is earlier than 6.5.22.0 or earlier than 2024.11.0 for the corresponding release track.
-
Verify AEM 6.5.x version numberIn AEM 6.5.x, navigate to the Help menu in the top-right corner and select About Adobe Experience Manager, or access /system/console/configMgr and locate the Product Information component.Affected if Version displayed is 6.5.21 or any version number lower than 6.5.22.0.
-
Verify AEM as a Cloud Service or 2024 release versionCheck the version via the Cloud Manager UI under the Environment Details section, or access the AEM SDK version through the Developer Console at /system/console/status-productinfo.Affected if Version displayed is earlier than 2024.11.0.
-
Inspect for exposed DOM injection pointsReview custom AEM components, HTL templates, or client-side JavaScript that handle URL parameters or user-supplied input. Look for code using document.write, innerHTML, or similar DOM manipulation methods without proper sanitization.Affected if Custom components or templates accept URL parameters or user input and render content directly into the DOM without output encoding.
-
Check for absence of Content Security Policy headersInspect HTTP response headers on AEM pages using browser developer tools (Network tab) or by running: curl -I https://your-aem-instance. Look for the Content-Security-Policy header.Affected if No CSP header is present in HTTP responses, meaning the environment lacks the mitigation layer for XSS execution.
The environment is affected if the installed AEM version is below 6.5.22.0 or below 2024.11.0, and the deployment contains components that render unsanitized input directly into the DOM.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.22.02024.11.0
Apply the vendor patch (upgrade to AEM 6.5.22 or later if available) and implement Content Security Policy (CSP) headers to mitigate XSS execution. Until patched, users should avoid clicking untrusted links.
AEM 6.5.22.0 or later (6.5.x track); AEM 2024.11.0 or later (2024.x track)
- Identify your current Adobe Experience Manager version and track (6.5.x or 2024.x)
- Download Adobe Experience Manager 6.5.22.0 or later for the 6.5.x track
- Download Adobe Experience Manager 2024.11.0 or later for the 2024.x track
- Review the Adobe Experience Manager release notes for any known issues before upgrading
- Perform a backup of your AEM instance and content repository
- Test the upgrade in a staging environment before deploying to production
- Execute the upgrade following Adobe's standard upgrade documentation
- Verify the XSS vulnerability is resolved by testing with the previously vulnerable URL patterns
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-52860 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-52860 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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