dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26086

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 where malicious JavaScript can be injected via a crafted URL. The attack requires social engineering to convince a victim to click a malicious link, and the script executes within the victim's browser context.

MitigationApply the vendor patch (AEM 6.5.21 or later) to address the XSS vulnerability. Until patched, users should avoid clicking untrusted URLs referencing AEM 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
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 AEM version via system console
    Access the AEM System Information console at /system/console/bundles or check the version displayed on the AEM login page footer. The version is also visible in the product.info extension at /libs/granite/core/content/login.html (if accessible).
    Affected if The displayed version is 6.5.20 or earlier, or the version falls below 2024.5 (for newer release trains).
  2. Query the AEM version endpoint
    If API access is available, query the version endpoint or check the crx/packmgr/service.jsp for version information. Administrators can also check the com.adobe.granite.package.version in the OSGi console at /system/console/configMgr.
    Affected if The queried version number is less than 6.5.21 for the 6.5.x train, or less than 2024.5 for the quarterly release train.
  3. Inspect HTTP responses for reflected parameters
    Use browser developer tools or a proxy to capture HTTP requests and responses when navigating AEM pages with URL parameters (such as /editor.html, /libs/wcm/core/content/editor, or content pages). Observe if input parameters are reflected unsanitized in the response body.
    Affected if URL parameter values appear verbatim (unescaped) in the HTML response, indicating potential XSS vulnerability.

The environment is affected if the installed AEM version is below 6.5.21 or below 2024.5, and the application reflects URL parameters without proper encoding in web page responses.

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

Apply the vendor patch (AEM 6.5.21 or later) to address the XSS vulnerability. Until patched, users should avoid clicking untrusted URLs referencing AEM pages.

Recommended fix High confidence

AEM 6.5.21 or later; AEM as a Cloud Service 2024.5 or later

  1. Confirm current Adobe Experience Manager version by checking the AEM welcome page or system console
  2. For AEM 6.5.x line: Plan upgrade to version 6.5.21 or later
  3. For AEM as a Cloud Service: Ensure deployment uses the 2024.5 release or later (or the next available release that includes the CVE-2024-26086 fix)
  4. Schedule maintenance window for the upgrade following standard AEM upgrade procedures
  5. Test the upgrade in a non-production environment before deploying to production
  6. After upgrade, verify the reflected XSS vulnerability is remediated by testing the vulnerable endpoint

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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