dbcve.org
Experience ManagerApplication · Adobe

CVE-2024-36182

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 in form fields. Attackers can inject malicious JavaScript that persists in the system and executes when victims view affected pages in their browsers.

MitigationApply the vendor patch (AEM 6.5.21 or later) and implement input validation/sanitization on all form fields to prevent script 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. Check installed AEM version
    Access the AEM System Information console or check the version.properties file in the crx-quickstart folder. Compare the version number against the affected ranges: versions before 6.5.21 or releases before 2024.5
    Affected if The installed version is less than 6.5.21 or the 2024.5 release
  2. Identify if AEM Forms module is in use
    Verify whether the AEM Forms component is enabled on the instance by reviewing the installed packages in the Package Manager or checking the Felix Console for Forms-related bundles
    Affected if AEM Forms module is installed and active on the instance
  3. Review form field configurations for input validation
    Inspect the form field definitions in the CRX/DE repository under /libs or /apps for the specific forms in use. Check whether each form field has validation rules configured to sanitize user input
    Affected if Form fields lack input validation or sanitization rules configured
  4. Examine stored form data for malicious scripts
    Query the form data stored in the repository or database for patterns matching script tags, javascript: URIs, or other XSS payloads in form submission fields
    Affected if Form submissions contain persisted JavaScript code or HTML tags in input fields
  5. Check for unauthorized form definition changes
    Review the audit logs or version history of form container components in the CRX/DE repository to identify recent modifications that may have introduced vulnerable configurations
    Affected if Form definitions were modified without documented change control

You are affected if your AEM version is below 6.5.21 or prior to 2024.5 AND you have the Forms module enabled with form fields that lack input sanitization.

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

Apply the vendor patch (AEM 6.5.21 or later) and implement input validation/sanitization on all form fields to prevent script injection.

Recommended fix Moderate confidence

Adobe Experience Manager 6.5.21 or later, or 2024.5 or later

  1. 1. Back up your current Adobe Experience Manager instance, including the repository, database, and configurations
  2. 2. Download the fixed version of Adobe Experience Manager (6.5.21 or later for 6.x line; 2024.5 or later for 2024 line) from Adobe's official distribution or support portal
  3. 3. Stop the running AEM instance and any related services
  4. 4. Install the upgrade following Adobe's documented upgrade procedure for your specific version path
  5. 5. After installation, verify the AEM instance starts successfully
  6. 6. Test the previously vulnerable form fields to confirm the XSS vulnerability is remediated
  7. 7. Clear browser caches and test in multiple browsers to ensure the fix is effective
  8. 8. Monitor logs and system behavior post-upgrade for any anomalies
Caveat Review Adobe's release notes for the target version to check for any deprecated features, API changes, or migration requirements that may affect your customizations

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