dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26117

MEDIUM · 5.4 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 6.5.21 / 2024.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 · moderate confidence

Adobe Experience Manager versions 6.5.20 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. An attacker can craft a malicious URL pointing to a vulnerable AEM page; if convinced to visit this URL, the victim's browser will execute arbitrary JavaScript within the context of the vulnerable site.

MitigationUpgrade to Adobe Experience Manager version 6.5.21 or later, which contains the patched version. Alternatively, implement input validation and output encoding on affected endpoints to neutralize malicious script content.

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
Experience ManagerApplication
Affected:< 6.5.21< 2024.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed AEM version
    Access the AEM system information page at /system/console/product or check the crx-quickstart/crx-quickstart.properties file for the version property
    Affected if The version listed is 6.5.20 or earlier, or the version starts with a year prior to 2024 (e.g., 2024.1 through 2024.4)
  2. Verify version is below 6.5.21
    Compare your installed version number against the 6.5.21 threshold. This can be done via the AEM Web Console Product Info page or by inspecting the manifest file in the installation directory
    Affected if The installed version is 6.5.20, 6.5.19, or any 6.5.x version below 6.5.21
  3. Verify version is below 2024.5
    If using the yearly release model, confirm the specific year-based version number (e.g., 2024.1, 2024.2, 2024.3, 2024.4) from the AEM system console
    Affected if The installed version is a 2024.x release prior to 2024.5 (e.g., 2024.1, 2024.2, 2024.3, or 2024.4)
  4. Confirm AEM is accessible and running
    Verify the AEM instance is online and responding to requests. The XSS can only be triggered if the vulnerable AEM application is actively serving pages
    Affected if The AEM instance is running and accessible to users or administrators who could be tricked into clicking a malicious URL

You are affected if your AEM instance is running version 6.5.20 or earlier, or any 2024.x version prior to 2024.5, and the application is accessible to potential victims who could be lured into visiting a crafted malicious URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.21 / 2024.5 or later
Fixed in 6.5.212024.5
Interim mitigation

Upgrade to Adobe Experience Manager version 6.5.21 or later, which contains the patched version. Alternatively, implement input validation and output encoding on affected endpoints to neutralize malicious script content.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 or later (or 2024.5 release branch)

  1. Back up the current Adobe Experience Manager instance and associated content repositories before initiating any upgrade
  2. Review the official Adobe Experience Manager release notes for version 6.5.21 (or 2024.5 release) to understand new features, deprecated functionality, and any known migration requirements
  3. Test the upgrade in a non-production environment first to ensure compatibility with custom code, third-party integrations, and workflows
  4. Deploy the upgrade to production environments following Adobe's standard upgrade procedures
  5. Verify the reflected XSS vulnerability (CVE-2024-26117) is remediated by testing that malicious script content in URL parameters is no longer executed
Caveat Review Adobe's release notes for the target version for any deprecated features or migration requirements that may affect custom implementations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26117 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26117 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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