dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36201

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 · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into vulnerable form fields. The malicious script executes in victims' browsers when they browse to pages containing the compromised fields.

MitigationImplement input validation and output encoding on all form fields to sanitize user-supplied content, and consider adding Content Security Policy headers to mitigate XSS execution.

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 Adobe Experience Manager version
    Access the AEM Web Console (typically at /system/console/configMgr) or check the product version from the AEM Welcome page (help > version information). Compare the installed version against the affected ranges: versions before 6.5.21 or before the 2024.5 release.
    Affected if The installed version is lower than 6.5.21 or lower than 2024.5, placing the environment within the affected version range.
  2. Audit form components in use
    Review the AEM Forms implementation and identify adaptive form components, core form fields, or custom form containers that accept user input. Check the component hierarchy under /libs/fd/af/components or custom form paths in the content repository.
    Affected if Form components that accept user input are present and accessible to unauthenticated or low-privileged users.
  3. Verify input validation on form fields
    Inspect the form field component configurations in AEM or review the data model and validation rules applied to each field. Check if server-side input validation and output encoding are configured for the form fields.
    Affected if Form fields lack server-side input validation or output encoding, allowing unsanitized user-supplied content to be stored.
  4. Inspect stored form submissions for malicious content
    Query the AEM content repository (using CRXDE Lite or a repository query) under the form submission data paths to identify any stored scripts or unusual HTML/JavaScript content within form field values.
    Affected if Form submission data contains unescaped HTML or JavaScript code, indicating successful exploitation or existing malicious entries.

The environment is affected if AEM version is below 6.5.21 or below 2024.5 AND form fields with user input are exposed without proper input validation and 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

Implement input validation and output encoding on all form fields to sanitize user-supplied content, and consider adding Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.21 or later, or AEM 2024.5 or later

  1. 1. Back up the current Adobe Experience Manager instance and repository
  2. 2. Review the Adobe Experience Manager 6.5.21 release notes at helpx.adobe.com for complete security fixes
  3. 3. Upgrade AEM from version 6.5.20 or earlier to version 6.5.21 or later
  4. 4. Alternatively, if using the newer release cadence, upgrade to 2024.5 or later
  5. 5. After upgrade, verify the XSS protection by testing that malicious scripts in form fields are properly escaped
  6. 6. Validate that all other functionality remains intact
Caveat Standard AEM minor version upgrade; review custom code compatibility with 6.5.21 or 2024.5 release

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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