CVE-2024-26089
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, as the victim needs to visit a web page with a maliciously crafted script.
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 confidenceDOM-based Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows execution of arbitrary JavaScript in victim's browser context through maliciously crafted scripts embedded in web pages.
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.
-
Identify installed AEM versionAccess the AEM system information console or check the version.properties file in the AEM installation directory to retrieve the exact version numberAffected if Version is 6.5.20 or earlier, or version is earlier than 2024.5 in the 2024 release cycle
-
Compare against vulnerable version rangesMatch the installed version against the affected ranges: 6.5.x versions below 6.5.21, or 2024.x versions below 2024.5Affected if Installed version is less than 6.5.21 or less than 2024.5
The environment is affected if Adobe Experience Manager is running a version below 6.5.21 (for 6.5.x branch) or below 2024.5 (for 2024 releases).
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
Upgrade Adobe Experience Manager to version 6.5.21 or later to obtain the security patch; alternatively apply the specific hotfix for CVE-2024-26089.
Adobe Experience Manager 6.5.21 or later (or 2024.5+ for newer branch)
- 1. Back up your current Adobe Experience Manager instance and content repository
- 2. Review Adobe's upgrade documentation for your current version to ensure compatibility
- 3. Upgrade Adobe Experience Manager to version 6.5.21 or later (for 6.5.x branch)
- 4. Alternatively, upgrade to 2024.5 or later (for the newer release branch)
- 5. After upgrade, verify that the AEM instance starts successfully
- 6. Test critical workflows to confirm functionality is intact
- 7. Validate that the XSS vulnerability is no longer present by reviewing the fixed release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26089 — 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-26089 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