dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36225

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 in form fields. Attackers can inject malicious JavaScript into these fields, which persists on the server and executes in victim users' browsers when they view the affected page.

MitigationUpgrade Adobe Experience Manager to a version beyond 6.5.20 as per Adobe's official security bulletin, or apply available security patches. Implement output encoding and input validation on affected form fields as a 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. Check Adobe Experience Manager version
    Navigate to the AEM Welcome page or use the system information console (typically at /system/console/systeminfo) to view the installed AEM version and build number.
    Affected if The installed version is older than 6.5.21 or older than the 2024.5 release (for Cloud Service).
  2. Identify custom form field components
    Review the /apps directory in CRXDE Lite or use the Component Finder to locate custom form components, particularly those that handle user input in form fields (text fields, textareas, dropdowns).
    Affected if Custom form components exist that do not implement output encoding on user-supplied values.
  3. Inspect stored form data for malicious scripts
    Query the JCR (Java Content Repository) using tools like CRXDE Lite or the Query debugger to examine stored values in form submission nodes (typically under /content/usergenerated or custom form containers). Look for script tags, javascript: URIs, or event handler attributes in field values.
    Affected if Form submission nodes contain unsanitized HTML or script tags in field values.
  4. Review form field input validation configuration
    Examine the form container configuration or Edit dialog of the affected form components. Check if Input Validation (Granite DataTypes or custom validation) is configured, and review any custom validation scripts.
    Affected if Form fields lack input validation rules or allow HTML content without sanitization.

A user is affected if their AEM installation is version 6.5.20 or earlier (or pre-2024.5 for Cloud) AND they have custom form components that store user input without output encoding or input validation.

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 beyond 6.5.20 as per Adobe's official security bulletin, or apply available security patches. Implement output encoding and input validation on affected form fields as a compensating control.

Recommended fix High confidence

AEM 6.5.21 or AEM 2024.5 (either version addresses the vulnerability)

  1. Verify current AEM version by checking the About Adobe Experience Manager page in the system console
  2. Review the AEM 6.5.21 release notes or 2024.5 release notes for changes relevant to your implementation
  3. Create a full backup of the AEM repository (crx-quickstart) and database
  4. Test the upgrade in a non-production environment first
  5. Ensure all custom code and third-party integrations are compatible with the target version
  6. Execute the upgrade following Adobe's standard upgrade procedure for your deployment type (jar upgrade or crx2oak migration)
  7. After upgrade, verify that the XSS protection is working by testing the vulnerable form fields with a non-malicious script payload
  8. Clear AEM caches and rebuild any search indexes if necessary
Caveat AEM upgrades may require testing of custom components and integrations; review release notes for deprecated features or API changes in the target version

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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