CVE-2024-26064
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.19 and earlier are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into a webpage. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable script. This could result in arbitrary code execution in the context of the victim's browser. Exploitation of this issue requires user interaction.
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.19 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. The vulnerability allows an attacker to inject malicious JavaScript into web pages served by AEM. When victims browse to pages containing the vulnerable script, the attacker's JavaScript executes in their browsers, enabling arbitrary code execution in the context of the victim's session.
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.20.0< 2024.3.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 AEM installed versionAccess the AEM System Information console at /system/console/webbundle or check the version.properties file in the crx-quickstart directory. Alternatively, append /libs/granite/core/content/login.html?debug=true to your AEM URL to view version info.Affected if The version displayed is earlier than 6.5.20.0 or earlier than 2024.3.0 (for cloud/2024 releases)
-
Confirm AEM edition and release typeVerify whether the instance is AEM 6.5 on-premise or AEM as a Cloud Service, as version numbering differs between them. Check the welcome page footer or system console for the full build version string.Affected if The instance is on 6.5.x with build version below 6.5.20.0, or the cloud release is before the March 2024 (2024.3.0) release
-
Locate vulnerable DOM-handling componentsReview custom OSGi components, Sling models, or HTL templates that handle user-provided input and render it directly into the page DOM without server-side encoding. Check /apps and /libs for components using unsafe JavaScript insertion points.Affected if Custom or overlayed components exist that inject request parameters or content directly into HTML without contextual encoding
-
Verify public-facing content deliveryDetermine if the AEM instance serves published content to unauthenticated users through the dispatcher or publish tier. DOM-based XSS requires the vulnerable script to be rendered when victims browse affected pages.Affected if The AEM publish tier or dispatcher is accessible to external users who could trigger the malicious script
Your AEM installation is affected if the installed version is below 6.5.20.0 (for 6.5 on-premise) or below 2024.3.0 (for cloud releases), and the vulnerable DOM injection point exists in your codebase or AEM's out-of-box components accessible to end users.
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.20.02024.3.0
Upgrade Adobe Experience Manager to version 6.5.20 or later to obtain the security patch. Review and sanitize any custom components or overlays that may handle user input in the DOM.
6.5.20.0 (or 2024.3.0 for newer branch)
- Identify the current Adobe Experience Manager version installed in your environment
- Determine which release branch you are on (6.5.x LTS or 2024.x cloud release)
- Create a complete backup of the current AEM instance including repository, database, and configurations
- Test the upgrade in a non-production environment before applying to production
- Upgrade AEM to version 6.5.20.0 or later (for 6.5.x LTS branch) or version 2024.3.0 or later (for 2024.x release)
- After upgrade, verify that the XSS vulnerability is resolved by testing the affected endpoint
- Deploy the validated upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26064 — 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-26064 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