dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26101

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 6.5.20.0 / 2024.3.0 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.19 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 confidence

Adobe Experience Manager versions 6.5.19 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability. The vulnerability allows an attacker to embed malicious JavaScript into a URL pointing to a vulnerable AEM page; when a victim clicks the crafted URL, the script executes in their browser context.

MitigationUpgrade Adobe Experience Manager to version 6.5.20 or later to obtain the vendor patch. Additionally, implement input validation and output encoding on affected endpoints, and consider deploying a WAF rule to block XSS attack patterns as a compensating control until the patch is applied.

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.20.0< 2024.3.0

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. Confirm Adobe Experience Manager is present
    Access the AEM login page or welcome page (typically at the root URL of the server). If AEM is running, you will see the AEM login screen or the AEM welcome page.
    Affected if The page returns an AEM login or welcome interface, confirming an AEM instance is accessible.
  2. Identify the installed AEM version
    Append '/system/console/bundles' to your AEM base URL and log in as an administrator. The version is often displayed on the bundles page or can be found in the 'About Adobe Experience Manager' section accessible from the AEM welcome page (top-right menu > About Adobe Experience Manager).
    Affected if You are unable to retrieve the version or the version shown is lower than 6.5.20.0 for the 6.5.x branch, or lower than 2024.3.0 for the 2024.x branch.
  3. Verify the version against affected ranges
    Compare your installed version number to the affected ranges: versions earlier than 6.5.20.0 (6.5.x branch) or versions earlier than 2024.3.0 (2024.x branch) are vulnerable.
    Affected if The installed version is 6.5.19 or earlier, or 2024.2 or earlier.
  4. Check for external-facing AEM endpoints
    Identify if AEM is exposed externally (internet-facing or DMZ). Check your network configuration and firewall rules to determine if the AEM publish or author instance is accessible from outside the trusted network.
    Affected if AEM is directly accessible from untrusted networks without proper WAF filtering, increasing the likelihood of the reflected XSS being exploitable.

Your environment is affected if Adobe Experience Manager is running and the installed version falls below 6.5.20.0 (for 6.5.x releases) or below 2024.3.0 (for 2024 releases).

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.20.0 / 2024.3.0 or later
Fixed in 6.5.20.02024.3.0
Interim mitigation

Upgrade Adobe Experience Manager to version 6.5.20 or later to obtain the vendor patch. Additionally, implement input validation and output encoding on affected endpoints, and consider deploying a WAF rule to block XSS attack patterns as a compensating control until the patch is applied.

Recommended fix High confidence

6.5.20.0 (for 6.5.x line) or 2024.3.0 (for cloud release)

  1. Upgrade Adobe Experience Manager to version 6.5.20.0 or later for the 6.5.x release line
  2. Alternatively, upgrade to version 2024.3.0 or later for the cloud release line
  3. After upgrading, verify the fix by testing the previously vulnerable endpoint with encoded payloads to confirm XSS is no longer executable
  4. Review Adobe's release notes for the target version to ensure all security patches are applied

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26101 — 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-26101 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