CVE-2024-26116
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 are affected by a reflected Cross-Site Scripting (XSS) vulnerability. If an attacker is able to convince a victim to visit a URL referencing a vulnerable page, malicious JavaScript content may be executed within the context of the victim's browser.
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 are affected by a reflected Cross-Site Scripting (XSS) vulnerability. The flaw allows an attacker to inject malicious JavaScript into URL parameters. When a victim is tricked into visiting a specially crafted URL pointing to a vulnerable AEM page, the malicious script executes within the victim's browser context.
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.
-
Locate the AEM version fileAccess the version.properties file in the crx-quickstart directory or check the Adobe Experience Manager Web Console (Help > About).Affected if The file cannot be found or AEM version information is not displayed.
-
Identify the installed AEM versionRead the version number from the version.properties file (typically at /crx-quickstart/org/apache/felix/version.properties) or note the version displayed in the About Adobe Experience Manager page.Affected if You cannot retrieve a version number from the AEM instance.
-
Compare against affected versionsCheck if the installed version is 6.5.x and below 6.5.21, or if it is a 2024.x release and below 2024.5.Affected if The installed version is 6.5.20 or earlier, or 2024.4 or earlier.
-
Verify the instance is accessibleConfirm the AEM instance is running and reachable via HTTP/HTTPS on its configured port.Affected if The AEM instance is not running or cannot be accessed.
You are affected if your Adobe Experience Manager instance is running version 6.5.20 or earlier, or version 2024.4 or earlier.
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 to a patched Adobe Experience Manager version (6.5.21 or later). Additionally, implement output encoding on user-supplied parameters and deploy Content Security Policy (CSP) headers to mitigate XSS risks.
AEM 6.5.21 (for 6.5.x line) or AEM 2024.5 (for newer release track)
- Identify your current Adobe Experience Manager version in AEM About information
- If running AEM 6.5.x line: upgrade to version 6.5.21 or later
- If running AEM newer release track: upgrade to version 2024.5 or later
- After upgrade, verify the installed version matches the target fixed release
- Test that the XSS vulnerability is no longer present in affected endpoints
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-26116 — 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-26116 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