CVE-2024-26037
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.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 typically requires user interaction, such as convincing a user to click on a specially crafted link or to submit a malicious form.
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.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. This client-side injection flaw allows attackers to inject malicious JavaScript that executes within victims' browsers by manipulating the Document Object Model, typically through crafted URLs or form submissions.
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.21< 2024.5CVSS 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 Welcome page or check the version information via the Felix console at /system/console/bundles, or look for the version manifest in the installation directory. The version is typically displayed on the AEM landing page or can be retrieved via the CRXDE Lite interface.Affected if The installed version is 6.5.20 or earlier, or the version is earlier than 2024.5 for the quarterly release track.
-
Verify AEM service pack levelCheck the installed service pack by navigating to /system/console/bundles or reviewing the crx-quickstart/package_share folder for installed packages. The file 'installer' or package list will show the exact service pack version applied.Affected if The service pack version is lower than 6.5.21 or the cumulative fix pack is below the patched release.
-
Inspect Content Security Policy configurationReview the Apache Sling or Adobe Granite CSRF filter configuration files, typically found in /libs/granite/csrf/configuration or via the OSGi console at /system/console/configMgr. Look for the 'Adobe Granite CSRF Filter' or custom CSP header configurations.Affected if No Content Security Policy headers are configured or the CSP is set to overly permissive values that allow inline script execution.
-
Check for vulnerable form or component pathsReview custom AEM components that handle user input through query parameters or form submissions. Examine any components that directly manipulate the DOM using JavaScript, particularly those in /apps or /libs that process URL parameters without sanitization.Affected if Custom or out-of-the-box AEM components accept user input and reflect it back into the DOM without proper encoding or sanitization.
-
Audit client-side libraries and scriptsExamine the client libraries in /etc/clientlibs or custom script files for unsafe DOM manipulation practices. Look for uses of innerHTML, document.write, or similar methods that could be influenced by URL parameters.Affected if Client-side scripts directly insert unsanitized user-controlled data into the DOM.
Your environment is affected if you are running Adobe Experience Manager version 6.5.20 or earlier (or a 2024.x release before the patched version) and have components or scripts that reflect user input into the DOM without sanitization.
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.212024.5
Apply the Adobe security patch for AEM 6.5.20 and implement Content Security Policy (CSP) headers as defense-in-depth. Additionally, educate users about risks of clicking untrusted links.
AEM 6.5.21 (for 6.5.x branch) or AEM 2024.5 (for continuous release track)
- 1. Identify the current Adobe Experience Manager version by checking /system/console or the crx/packmgr interface
- 2. If running AEM 6.5.x branch, plan upgrade to version 6.5.21
- 3. If running the continuous release track, plan upgrade to version 2024.5
- 4. Perform a complete backup of the AEM repository (crx-quickstart) and database before upgrading
- 5. Test the upgrade in a non-production environment first
- 6. Apply the upgrade following Adobe's standard upgrade procedures (see helpx.adobe.com for detailed documentation)
- 7. Verify the upgrade was successful by confirming the new version in /system/console/about
- 8. Validate that the XSS vulnerability is resolved by testing the previously vulnerable endpoint
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26037 — 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-26037 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