CVE-2024-36191
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 · moderate confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.20 and earlier allows attackers to inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the malicious script executes in their browsers.
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.
-
Verify Adobe Experience Manager versionAccess the AEM Welcome page or check the product version via the Help menu, or query the version endpoint at /system/console/branding. Compare your version number against the affected ranges: versions below 6.5.21 or below 2024.5.Affected if Your installed version is 6.5.20 or earlier, or falls below the 2024.5 release.
-
Identify Forms or Adaptive Forms usageNavigate to the Forms section in AEM Assets or use CRX/DE to check for presence of adaptive form fragments under /content/forms/af or classic form assets under /content/dam/formsanddocuments.Affected if Forms or Adaptive Forms modules are created or enabled in your AEM instance.
-
Inspect custom form field componentsUsing CRX/DE Lite, examine any custom form components under /apps or /libs that handle user input. Check the JSP or HTL rendering code for proper output encoding of field values.Affected if Custom form components exist that do not use AEM's built-in XSS protection APIs like xssAPI.encodeForHTMLAttr().
-
Review published form content for injected scriptsQuery the publish instance repository or use the AEM Query Builder to search form content nodes for suspicious patterns like <script> tags or event handlers such as onload=, onerror=, or javascript: prefixes in field values.Affected if Form field data in the repository contains unsanitized script tags or javascript: URIs.
You are affected if your AEM version is below 6.5.21 (or below 2024.5) and you have Forms or Adaptive Forms enabled with form fields that accept user input.
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
Upgrade Adobe Experience Manager to a version beyond 6.5.20 that includes the security patch, and implement input validation and output encoding for all form fields to prevent XSS injection.
AEM 6.5.21 or later / AEM as a Cloud Service 2024.5 or later
- Verify current Adobe Experience Manager version by checking the AEM console or system information
- Plan upgrade schedule following Adobe's recommended upgrade process
- Upgrade AEM 6.5.x installations to version 6.5.21 or later
- Alternatively, upgrade to AEM as a Cloud Service 2024.5 or later if using the cloud version
- After upgrade, verify the fix by testing form fields that were previously vulnerable
- Review Adobe Experience Manager 6.5.21 release notes for any additional security fixes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.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 $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36191 — 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-36191 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