CVE-2024-26090
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 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 confidenceAdobe Experience Manager versions 6.5.20 and earlier contain a DOM-based Cross-Site Scripting (XSS) vulnerability. The flaw allows attackers to inject malicious JavaScript that executes in the victim's browser context by manipulating the DOM based on untrusted input, likely through URL parameters or client-side code handling.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Determine your AEM versionAccess the AEM System Console at /system/console/about or check the Help menu > About Adobe Experience Manager to view the installed version numberAffected if The installed version is 6.5.20 or earlier, or the version falls below the 2024.5 release
-
Identify components using URL parameters in DOM manipulationReview custom client-side JavaScript code and Sightly/HTL templates that read URL parameters (such as query strings or path selectors) and directly insert them into the DOM without sanitizationAffected if Custom or extended components use unvalidated URL parameter data to modify the DOM
-
Check for untrusted link handling configurationsAudit any AEM components or third-party integrations that process external URL parameters and render them in HTML output without proper encodingAffected if Components accept and render URL parameter values directly into page output without input validation or output encoding
-
Review published exposureIf running in publish mode, verify whether publicly accessible pages contain components that dynamically manipulate the DOM based on user-supplied input from the request URLAffected if The publish instance serves pages with DOM-manipulating components accessible to unauthenticated users
Your environment is affected if the installed AEM version is earlier than 6.5.21 (or earlier than the 2024.5 release) AND the deployment includes components or custom code that manipulate the DOM using untrusted input from URL parameters.
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 vendor patch (upgrade to a version newer than 6.5.20) or implement input validation/sanitization on affected AEM components that handle DOM manipulation. Users should be cautioned against clicking untrusted links.
Adobe Experience Manager 6.5.21 or later, or AEM as a Cloud Service 2024.5 or later
- Identify the current Adobe Experience Manager version running in your environment
- For AEM 6.5 on-premise installations: Plan upgrade to version 6.5.21 or later
- For AEM as a Cloud Service: Plan upgrade to version 2024.5 or later
- Create a full backup of the current AEM instance including content repository and configurations
- Test the upgrade in a non-production/staging environment to verify compatibility
- Verify all custom code, templates, and integrations work correctly after upgrade
- Deploy the validated upgrade to production environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26090 — 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-26090 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