dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26111

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 · high confidence

Adobe Experience Manager versions 6.5.20 and earlier contain a reflected Cross-Site Scripting (XSS) vulnerability where malicious JavaScript code can be injected into the response when a victim is tricked into visiting a specially crafted URL. The payload is reflected back from the server without proper sanitization, allowing execution in the victim's browser context.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.20. Additionally, implement input validation, output encoding, and Content Security Policy headers to mitigate XSS attacks.

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 the installed Adobe Experience Manager version
    Access the AEM information page by navigating to /libs/cq/core/content/info.json or /libs/granite/core/content/login.html in a browser. Alternatively, access the OSGi Web Console at /system/console/bundles and search for the 'com.day.commons.javadoc' bundle to view the product version.
    Affected if The version displayed is 6.5.20 or earlier, or falls below 2024.5 (for cloud/flex releases).
  2. Verify the product version against affected ranges
    Compare the discovered version number to the affected ranges: any version lower than 6.5.21 (for 6.x releases) or any version lower than 2024.5 (for yearly releases) is considered vulnerable.
    Affected if The installed version is < 6.5.21 or < 2024.5.
  3. Confirm the AEM instance is accessible over the network
    Attempt to access the AEM instance login page or any public-facing endpoint using a standard HTTP GET request. Verify the server responds with an Adobe Experience Manager page.
    Affected if The instance is reachable and running, meaning the reflected XSS could potentially be triggered if a user visits a maliciously crafted URL.

If the installed AEM version is below 6.5.21 (for 6.x lines) or below 2024.5 (for yearly releases), the environment is affected by this reflected XSS vulnerability.

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 Adobe Experience Manager to a version newer than 6.5.20. Additionally, implement input validation, output encoding, and Content Security Policy headers to mitigate XSS attacks.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 (on-premise) or Adobe Experience Manager 2024.5 (cloud)

  1. Backup your current Adobe Experience Manager instance and database
  2. Review the Adobe Experience Manager 6.5.21 release notes for any migration requirements
  3. Download Adobe Experience Manager 6.5.21 or later from the Adobe distribution center
  4. Follow Adobe's standard upgrade procedure for AEM 6.5.x
  5. Verify the upgrade was successful by checking the version in the AEM web console
  6. Test critical workflows to ensure functionality is preserved after the upgrade

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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