dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26055

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 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 triggers the malicious script.

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 DOM-based Cross-Site Scripting (XSS) vulnerability that allows attackers to execute arbitrary JavaScript in victim's browsers via malicious links or forms. The attack requires user interaction to trigger.

MitigationUpgrade AEM to a version newer than 6.5.20. Additionally, implement input validation and output encoding on affected endpoints to mitigate XSS vectors.

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. Locate AEM version information
    Access the AEM Welcome page at /libs/cq/core/content/welcome.html or check the version displayed in the AEM login screen footer. Alternatively, check the version.properties file located in the crx-quickstart/conf directory.
    Affected if The displayed version is 6.5.20 or earlier, or the version is a 2024.x release earlier than 2024.5.
  2. Verify exact AEM version via System Console
    Navigate to /system/console/bundles and look for the 'Adobe Experience Manager' or 'com.day.cq' bundle entries in the bundle list. The version is also visible in the AEM startup logs under crx-quickstart/logs/error.log.
    Affected if The version number shown is below 6.5.21 for the 6.5.x branch, or below 2024.5 for the newer release cadence.
  3. Identify if the vulnerable endpoint is accessible
    Check whether unauthenticated or low-privilege users can access endpoints that handle user-supplied input without proper encoding, particularly custom components or third-party integrations that render content in the DOM.
    Affected if The AEM instance exposes web content endpoints that accept user input and render it back without sufficient output encoding.
  4. Check for recent security-related hotfixes
    Review installed AEM hotfixes in the Package Manager (accessible via /crx/packmgr/list.jsp) or the System Console's Product Info tab (/system/console/productinfo) to see if CVE-2024-26055-specific patches have been applied.
    Affected if No security hotfix addressing CVE-2024-26055 is installed and the AEM version falls within the affected ranges.

An AEM installation is affected if it runs version 6.5.20 or earlier in the 6.5.x branch, or any version prior to 2024.5 in the newer release cadence, and exposes endpoints that render user input without proper output encoding.

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 AEM to a version newer than 6.5.20. Additionally, implement input validation and output encoding on affected endpoints to mitigate XSS vectors.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 (for 6.5.x line) or Adobe Experience Manager 2024.5 (for as a Cloud Service)

  1. 1. Back up your current AEM instance and verify backup integrity before proceeding.
  2. 2. Review Adobe's official upgrade documentation for Experience Manager at helpx.adobe.com.
  3. 3. For AEM 6.5.x line: Upgrade to version 6.5.21 or later.
  4. 4. For AEM as a Cloud Service: Upgrade to version 2024.5 or later.
  5. 5. After upgrade, verify the XSS vulnerability is resolved by testing with the identified attack vectors.
  6. 6. Validate that custom code and integrations function correctly post-upgrade.
Caveat Standard upgrade considerations apply - review release notes for deprecations and ensure custom code compatibility

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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