CVE-2024-36170
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 vulnerability in form fields. Attackers can inject malicious JavaScript that executes in victims' browsers when they view pages containing the compromised form fields.
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 the installed Adobe Experience Manager versionAccess the AEM Help menu or system information console (typically via /system/console or the About Adobe Experience Manager page) to view the current version numberAffected if The installed version is 6.5.20 or earlier, or falls below version 2024.5
-
Identify if AEM Forms or form field components are in useReview your AEM content structure or Forms configuration to determine if form-based content (Adaptive Forms, Foundation Forms, or custom form components) is deployed on your instanceAffected if Form fields are present and the AEM version is vulnerable as determined in step 1
-
Inspect form field definitions for potential XSS injection pointsExamine the XML configuration or content XML files associated with form fields (commonly found under /content or /etc in the repository) for any unescaped script tags or event handler attributesAffected if Unescaped script content or dangerous event handlers (such as onerror, onload) are found in form field definitions
-
Review published pages that render form contentUse the AEM Content Search or examine published content to check if any form field values contain encoded or unencoded script elementsAffected if Stored JavaScript code or script tags appear within form field values in published content
A user is affected if their AEM version is below 6.5.21 or 2024.5 AND they have form fields in their environment that could contain injected malicious scripts.
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 to apply the security patch; additionally, implement input validation and output encoding on form fields, and consider Content Security Policy headers.
AEM 6.5.21 or AEM 2024.5 (or later)
- Upgrade Adobe Experience Manager to version 6.5.21 or later for the 6.5.x release line
- Alternatively, upgrade to the 2024.5 release or later
- After upgrading, verify that the form fields no longer allow script injection by testing with a harmless XSS payload
- Confirm the patch was applied by checking the AEM version in the Help > About Adobe Experience Manager section
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36170 — 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-36170 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