dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26066

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 stored Cross-Site Scripting (XSS) vulnerability that could be abused by an attacker to inject malicious scripts into vulnerable form fields. Malicious JavaScript may be executed in a victim’s browser when they browse to the page containing the vulnerable field.

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

A stored Cross-Site Scripting vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into form fields. The malicious payload is persisted in the system and executes in victims' browsers when they navigate to pages containing the affected fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to apply the vendor patch. Additionally, implement output encoding on form fields and consider Content Security Policy headers as defense-in-depth.

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. Check the installed Adobe Experience Manager version
    Access the AEM Web Console at /system/console or use the Package Manager to view the product version. This is typically visible on the Welcome screen or via the 'version' servlet at /system/console/product
    Affected if The installed version is 6.5.20 or earlier, or falls below version 2024.5
  2. Confirm the exact version number against affected ranges
    Compare the discovered version to the vulnerable ranges: versions < 6.5.21 and versions < 2024.5 are affected
    Affected if The version is 6.5.20 or earlier, or a 2024.x version prior to the 2024.5 release
  3. Identify if Forms or Adaptive Forms components are deployed
    Review the AEM instance for any Adaptive Forms, Core Components Form, or Foundation Form implementations. Check the CRX/DE repository under /apps for form-related content packages or components
    Affected if Form components that accept user input are present in the environment
  4. Inspect form field configurations for input validation
    Examine the form field component configurations in the AEM authoring environment or in the corresponding XML/JSON configuration files under /conf or /apps. Verify whether server-side output encoding or input validation is configured
    Affected if Form fields lack proper output encoding or input validation configurations
  5. Audit persisted form data for suspicious payloads
    Query the AEM repository (CRX) or form submission storage for entries containing script tags, JavaScript: URLs, or event handler attributes (onload, onerror, onclick) in form field values
    Affected if Malicious JavaScript payloads are found stored in form submission data

An AEM instance is affected if it runs version 6.5.20 or earlier (or a 2024.x version below 2024.5) AND has form components that accept 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 Adobe Experience Manager to version 6.5.21 or later to apply the vendor patch. Additionally, implement output encoding on form fields and consider Content Security Policy headers as defense-in-depth.

Recommended fix High confidence

Adobe Experience Manager 6.5.21 (or later) / AEM as a Cloud Service 2024.5 or later

  1. 1. Back up the current AEM instance including repository, database, and configuration files
  2. 2. Review Adobe Experience Manager release notes for version 6.5.21 for any migration requirements
  3. 3. If using AEM 6.5.x on-premise, upgrade the instance to version 6.5.21 or later by applying the latest service pack
  4. 4. If using AEM as a Cloud Service, ensure the environment is running the 2024.5 release or later
  5. 5. After upgrade, verify that the XSS filter configurations are properly enabled in the OSGi settings
  6. 6. Test the fixed form fields to confirm malicious scripts are properly sanitized
  7. 7. Clear AEM cache and rebuild any search indexes post-upgrade
Caveat AEM upgrades may require content repository migration and compatibility checks for custom code; test thoroughly in staging 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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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