dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26091

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 →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Answer: are affected by a DOM-based Cross-Site Scripting (XSS) vulnerability. This vulnerability could allow an attacker to execute arbitrary JavaScript code in the context of the victim's browser session. Exploitation of this issue typically requires user interaction, such as convincing a victim to click on a specially crafted link or to submit a form that causes the vulnerable script to execute.

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 DOM-based Cross-Site Scripting (XSS) vulnerability where user-supplied input is improperly handled in the DOM, allowing attackers to inject malicious JavaScript that executes in the victim's browser context.

MitigationApply the vendor patch (AEM 6.5.21 or later) which addresses the XSS vulnerability. Additionally, implement input validation and output encoding for any custom code handling user input in DOM operations.

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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
    Navigate to the AEM Welcome page or check the com.adobe.granite.package version via the Felix Console (system/console/bundles). Alternatively, locate the 'cq-quickstart.properties' file in the AEM installation directory or check the 'manifest.json' in the crx-quickstart folder.
    Affected if The version number is lower than 6.5.21 or the year-based version is earlier than 2024.5 (for cloud or newer release tracks).
  2. Review custom code for DOM manipulation of user input
    Search the codebase (under /apps and /libs) for JavaScript files and JSP/HTL components that use innerHTML, outerHTML, insertAdjacentHTML, or similar DOM APIs with user-provided data from request parameters, form inputs, or content fragments.
    Affected if Custom code directly injects unencoded user input into the DOM via these methods.
  3. Inspect XSS protection configurations
    Check the OSGi configuration for 'Adobe Experience Manager HTML Library Manager' (com.adobe.granite.ui.clientlibs.HtmlLibraryManager) and the 'XSS API Configuration' (com.adobe.granite.xss). Verify if XSS protection is enabled and review any custom XSS filter rules.
    Affected if XSS protection is disabled or overly permissive custom rules allow script tag injection in DOM contexts.
  4. Audit content fragments and user-generated content handling
    Examine Experience Fragments, Content Services, or any custom endpoints that return user-supplied data as JSON or HTML. Check the dispatcher's cache configuration and any client-side templating logic.
    Affected if User content is rendered directly to the browser without server-side output encoding before being processed by client-side JavaScript.

You are affected if your AEM version is below 6.5.21 (or below 2024.5 for newer release tracks) AND custom code or configuration allows unencoded user input to flow into DOM operations in the browser.

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) which addresses the XSS vulnerability. Additionally, implement input validation and output encoding for any custom code handling user input in DOM operations.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x branch) or AEM 2024.5 (for Cloud Service)

  1. 1. Identify your current Adobe Experience Manager version in the AEM System Overview or about Adobe Experience Manager page
  2. 2. Determine if your version is affected: AEM 6.5.x versions before 6.5.21, or AEM versions before 2024.5
  3. 3. Perform a full backup of your AEM instance including repository, database, and configurations
  4. 4. For AEM 6.5.x users: Upgrade to AEM 6.5.21 or later by applying the latest Service Pack from Adobe's Software Distribution portal
  5. 5. For AEM as a Cloud Service users: Upgrade to 2024.5 release or later through the Cloud Manager or by requesting a release upgrade
  6. 6. After upgrade, clear browser caches and verify the XSS vulnerability is resolved
  7. 7. Test critical user workflows to ensure the upgrade does not break existing functionality
Caveat Service packs are typically backward-compatible cumulative updates, but always test in a staging environment before production deployment

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-26091 — 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-26091 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