dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36150

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victims' browsers when they navigate to pages containing the compromised form fields.

MitigationUpgrade to Adobe Experience Manager 6.5.21 or later to obtain the security patch. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize all user inputs in custom form fields as a defense-in-depth measure.

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 installed Adobe Experience Manager version
    Access the AEM System Information console at /system/console/systeminfo or check the version.properties file in the crx-quickstart folder. Look for the exact version number displayed.
    Affected if The installed version is 6.5.20 or earlier, or any version prior to the 2024.5 release.
  2. Confirm AEM Forms or custom form components are in use
    Navigate to the AEM Forms console at /aem/forms or inspect the /apps directory for custom form field components. Check if any Adaptive Forms, Core Components form fields, or custom form implementations are present.
    Affected if AEM Forms or any custom form field components are deployed and accessible to users.
  3. Review form field input validation configuration
    Inspect the form field component configurations in CRX/DE at /apps or /libs. Check the properties of Adaptive Form fields or Core Components for validation constraints. Look for是否存在 xml schema or custom validation rules.
    Affected if Form fields lack proper input validation or sanitization rules configured.
  4. Audit recent form submissions for suspicious content
    Use CRX/DE Lite to search form data in the repository. Check nodes under /content/forms/fp or custom form submission paths. Look for script tags, javascript: URIs, or event handlers in field values.
    Affected if Any form submissions contain persisted malicious scripts or suspicious HTML/JavaScript payloads.

Your environment is affected if you run AEM version 6.5.20 or earlier (or pre-2024.5) AND have forms with user-input fields that accept and store unvalidated content.

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 to Adobe Experience Manager 6.5.21 or later to obtain the security patch. Additionally, implement Content Security Policy (CSP) headers and validate/sanitize all user inputs in custom form fields as a defense-in-depth measure.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x branch) or 2024.5 (for newer release train)

  1. Identify the current Adobe Experience Manager version in use
  2. Backup the AEM instance including the repository and configuration files
  3. Schedule a maintenance window for the upgrade
  4. If running AEM 6.5.x branch: Upgrade to AEM 6.5.21 or later
  5. If running the newer release train: Upgrade to 2024.5 or later
  6. After upgrade, verify the AEM instance starts successfully
  7. Test the application functionality to ensure no regressions
  8. Confirm the XSS vulnerability is remediated by verifying form field input handling
Caveat Standard AEM upgrade considerations apply - test thoroughly in non-production first, 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
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA5.0 h
33.0 hours of engineering $5,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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