CVE-2024-36202
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 · uneditedAdobe 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 confidenceAdobe 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 vulnerable form inputs, which persists in the system and executes when users view the affected page.
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< 6.5.21< 2024.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check your Adobe Experience Manager versionAccess the AEM Welcome page or check the version.properties file in the crx-quickstart folder. You can also use the system console (/system/console/bundles) to confirm the AEM version installed.Affected if The installed version is 6.5.20 or earlier, or any version prior to the 2024.5 release.
-
Identify custom form components in useReview the /apps folder in CRXDE Lite for custom form field components or look for custom Adaptive Form configurations. Check content pages that contain form elements.Affected if Custom form components or Adaptive Form fields are present in the environment.
-
Review form field input handlingExamine the form submission handler or model for the custom form fields. Look for the code that processes form input before storage, specifically checking if input validation or sanitization is performed on submitted values.Affected if Custom form fields accept and store user input without validating or encoding the data.
-
Inspect stored form data for unencoded contentQuery the repository (using CRXDE Lite or a search) for form submission data or user-generated content stored in the repository. Look for entries containing script tags, javascript:, or other HTML/script elements.Affected if Stored form data contains raw HTML, script tags, or event handlers without encoding.
You are affected if your AEM version is below 6.5.21 or pre-2024.5 AND custom or Adaptive Form fields exist that store user input without proper validation or output encoding.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.5.212024.5
Update Adobe Experience Manager to version 6.5.21 or later. Additionally, implement input validation and output encoding on all custom form fields to prevent XSS.
AEM 6.5.21 or AEM 2024.5 (whichever matches your deployment type)
- Create a complete backup of the current AEM instance including repository, database, and configurations
- Set up a staging or development environment to test the upgrade before applying to production
- Download Adobe Experience Manager version 6.5.21 (for 6.x installations) or version 2024.5 (for Cloud Service/2024 releases) from the official Adobe distribution portal
- Run the upgrade installer following Adobe's standard upgrade documentation for your specific deployment type
- After upgrade, verify that the vulnerable form fields no longer accept and execute malicious script payloads
- Deploy the upgraded instance to production after successful validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36202 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36202 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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