dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36153

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

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 executes in victims' browsers when they navigate to pages containing the affected fields.

MitigationUpdate Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding on form fields to prevent XSS injection.

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 AEM version
    Navigate to AEM Welcome page > Tools > Operations > Web Console, or access /system/console/configMgr, or check the version from the AEM start page footer. Alternatively, check the crx-quickstart/package-version.properties file.
    Affected if The installed version is below 6.5.21 or below 2024.5 (for cloud/2024 releases).
  2. Confirm AEM Forms module is in use
    Check if Adobe AEM Forms is enabled by navigating to Tools > Forms or accessing /aem/forms. Inspect if custom form schemas or adaptive forms are configured.
    Affected if AEM Forms are actively configured and users can submit data through form fields.
  3. Review form field configurations for input validation
    Access Forms configuration at /libs/fd/fdm/components/editor/config, or inspect adaptive form models under /content/forms/af. Check if output encoding or input validation rules are explicitly defined on form fields.
    Affected if Form fields lack server-side input validation and output encoding configurations.
  4. Scan form submission content for malicious payloads
    Use AEM Query Builder or CRXDE Lite to search content repositories under /content/forms/submissions for stored script tags (for example, <script> elements or event handlers like onerror, onload). Query example: /jcr:root/content/forms/submissions//element(*, nt:unstructured) contains 'script'.
    Affected if Form submission data contains unsanitized script tags, javascript: URIs, or event handler attributes.

You are affected if your AEM version is below 6.5.21 (or below 2024.5) and your environment uses AEM Forms with custom or adaptive form fields that accept user input without strict 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

Update Adobe Experience Manager to version 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding on form fields to prevent XSS injection.

Recommended fix High confidence

AEM 6.5.21 (or AEM as a Cloud Service 2024.5+)

  1. Review Adobe Experience Manager release notes for version 6.5.21 (or 2024.5 if on the newer release line) to understand new features, fixed issues, and any known incompatibilities
  2. Create a full backup of the current AEM instance including the repository, database, and configurations
  3. Set up a staging or development environment mirroring production to test the upgrade before applying it to production
  4. Schedule appropriate maintenance window as AEM upgrades typically require downtime
  5. Download and install Adobe Experience Manager 6.5.21 or later (or 2024.5 or later for the newer release line) using the Adobe Software Distribution portal
  6. After upgrade, verify that custom code, third-party integrations, and workflows function correctly
  7. Clear all AEM caches and rebuild any search indexes as needed
  8. Monitor AEM error logs post-upgrade for any issues
Caveat Review custom code and third-party integrations for compatibility; major AEM upgrades may require code changes or affect existing workflows

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
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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