dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36155

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 (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 on the server and executes when other users browse to pages containing the compromised fields.

MitigationUpgrade Adobe Experience Manager to version 6.5.21 or later to obtain the vendor patch. Alternatively, implement strict input validation and output encoding on all form fields as an interim compensating control.

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 the installed Adobe Experience Manager version
    Access the AEM Web Console Help page at /system/console/help or navigate to Help > About Adobe Experience Manager in the AEM UI to view the version number
    Affected if The version shown is 6.5.20 or earlier, or falls below version 2024.5 (for the 2024 release track)
  2. Confirm AEM instance type and release track
    Check if the installation is on the 6.5 LTS track or the 2024 yearly release track. The 6.5.21 patch only applies to the 6.5.x LTS line
    Affected if Running 6.5.20 or earlier on the LTS track, or any version before 2024.5 on the yearly release track
  3. Identify deployed Adaptive Form or Form components
    Review the AEM Forms UI at /aem/forms.html or inspect the content repository under /content/forms for any Adaptive Form or Form Fragment components that accept user input
    Affected if Any Adaptive Forms are created and accessible to untrusted users without additional validation layers
  4. Verify input validation configuration on forms
    Review the Rule Editor or form model configuration for each form to confirm whether server-side validation rules are defined for all input fields
    Affected if Form fields lack server-side validation rules allowing arbitrary content submission
  5. Inspect for custom form field components
    Check /apps or /libs for any custom form field components or client libraries that handle form input, particularly those that may bypass AEM core encoding
    Affected if Custom form components exist that do not utilize AEM's standard encoding mechanisms for output

The environment is affected if the installed AEM version is 6.5.20 or earlier on the 6.5.x LTS track, or any version below 2024.5 on the yearly release track, and Adaptive Forms or custom form components that accept user input are in use.

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 obtain the vendor patch. Alternatively, implement strict input validation and output encoding on all form fields as an interim compensating control.

Recommended fix High confidence

AEM 6.5.21 (6.x line) or AEM 2024.5 (cloud/2024.x line)

  1. Identify the current Adobe Experience Manager version in use (6.x line or cloud/2024.x line)
  2. For AEM 6.x installations: Upgrade to Adobe Experience Manager 6.5.21 or later
  3. For AEM cloud/2024.x installations: Upgrade to Adobe Experience Manager 2024.5 or later
  4. Review and apply any Adobe release notes or migration considerations for the target version
  5. After upgrade, verify the new version is correctly installed
  6. Test that the stored XSS vulnerability is no longer exploitable in form fields
Caveat Review Adobe Experience Manager release notes for the target version for any migration requirements or breaking changes

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
  • Testing4.0 h
  • Review / QA2.0 h
24.0 hours of engineering $4,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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