dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36143

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

Adobe Experience Manager versions 6.5.20 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Attackers can inject malicious JavaScript into vulnerable form fields, which persists in the system and executes when legitimate users view pages containing the affected fields.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.20. Additionally, implement input validation and output encoding for form fields, and consider Content Security Policy headers to mitigate XSS risks.

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. Determine installed AEM version
    Navigate to AEM welcome page (/) or access /system/console/status/productinfo to retrieve the version number. Alternatively, check the version.properties file in the crx-quickstart folder.
    Affected if The version is 6.5.20 or earlier, or the version is below 2024.5 (for cloud/2024 releases).
  2. Identify Adaptive Forms or custom form components
    Check for the presence of Adaptive Forms by navigating to Forms > Forms & Documents in AEM Assets, or search for custom form components in the CRX/DE repository under /apps. Look for content fragments or form fragments that accept user input.
    Affected if AEM Forms or custom form components are present and the AEM version is in the affected range.
  3. Review form field configurations for missing output encoding
    In CRX/DE, examine the JSP or HTL files for form input components (such as text fields, textareas, or dropdowns) under /libs/foundation/components or custom form components. Check whether the values are rendered using proper encoding functions (for example, encodeForHTML or equivalent XSS protection).
    Affected if Form components use raw output (no encoding) when displaying submitted values back to users.
  4. Inspect stored form data for malicious scripts
    Query the repository using CRXDE or the Query Builder to search for stored form submissions containing script tags or JavaScript event handlers (such as <script>, onerror=, onload=, javascript:) in text fields.
    Affected if Form submissions in the repository contain unencoded script tags or JavaScript event handlers.

You are affected if your AEM version is below 6.5.21 (or below 2024.5 for cloud releases) AND you have Adaptive Forms or custom 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 a version newer than 6.5.20. Additionally, implement input validation and output encoding for form fields, and consider Content Security Policy headers to mitigate XSS risks.

Recommended fix High confidence

AEM 6.5.21 (for 6.5.x branch) or AEM 2024.5 (for Cloud/2024.x branch)

  1. Identify your current Adobe Experience Manager version by checking the Product Information in AEM (go to Help > About Adobe Experience Manager)
  2. For AEM 6.5.x installations: Plan upgrade to version 6.5.21 or later
  3. For AEM Cloud/2024.x installations: Plan upgrade to version 2024.5 or later
  4. Before upgrading, review Adobe's release notes and perform a full backup of the environment
  5. Test the upgrade in a staging environment before deploying to production
  6. Schedule maintenance window and deploy the upgrade
  7. After upgrade, verify that the XSS vulnerability is resolved by testing the affected form fields

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