dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-26067

MEDIUM · 5.4 CVSS v3.1 Published 2024-03-18
Fix available
A fix is available. Upgrade to 6.5.20.0 / 2024.3.0 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.19 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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.19 and earlier allows attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the malicious script executes in their browsers.

MitigationUpdate Adobe Experience Manager to version 6.5.20 or later to receive the security patch. Alternatively, implement input validation and output encoding on affected form fields to sanitize user-supplied content.

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.20.0< 2024.3.0

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 Adobe Experience Manager installed version
    Navigate to the AEM welcome page or access the system/console/info endpoint (usually /system/console/info) to view the product version. Alternatively, check the crx-quickstart/package.xml file or run 'java -jar cq-quickstart.jar -version' if the JAR is available.
    Affected if The installed version is below 6.5.20.0 (for 6.5.x branches) or below 2024.3.0 (for newer release trains)
  2. Identify form components in use
    Review the AEM instance for Adaptive Forms, Core Components Form (core/wcm/components/form/*), or Foundation Form (foundation/components/form/*) components deployed on publish or author instances. Check the CRX/DE repository under /apps for form-related components.
    Affected if Form components that accept user input are present and accessible on the instance
  3. Inspect form field input validation configuration
    In AEM Forms or Adaptive Forms editor, examine the field properties for specific form components. Check the XML model or edit configuration of Adaptive Form fields under /content/forms/af to verify if Input Validation and Output Encoding rules are configured.
    Affected if Form fields lack input validation rules or output encoding is not enabled on the field properties
  4. Search for existing malicious scripts in form data
    Query the AEM repository or form submission data stores for suspicious patterns. Use CRXDE or the Query tool to search nodes under /content/forms/* for common XSS payloads like '<script', 'javascript:', 'onerror=', 'onload=' in field values.
    Affected if Any form field data contains unsanitized script tags or event handler attributes

The environment is affected if the AEM version is below 6.5.20.0 or below 2024.3.0 AND the instance uses form components with fields that accept user input without proper input validation or output encoding configured.

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.20.0 / 2024.3.0 or later
Fixed in 6.5.20.02024.3.0
Interim mitigation

Update Adobe Experience Manager to version 6.5.20 or later to receive the security patch. Alternatively, implement input validation and output encoding on affected form fields to sanitize user-supplied content.

Recommended fix High confidence

AEM 6.5.20.0 or later; AEM as a Cloud Service 2024.3.0 or later

  1. Upgrade AEM 6.5.x installations to version 6.5.20.0 or later
  2. Upgrade AEM as a Cloud Service installations to version 2024.3.0 or later
  3. After upgrading, verify that the XSS vulnerability is remediated by testing form fields for proper input sanitization
  4. Validate that existing workflows and integrations function correctly post-upgrade
Caveat Review Adobe AEM 6.5.20 release notes and 2024.3.0 release notes for any breaking changes or deprecated features before upgrading

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