CVE-2024-36232
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 where malicious scripts can be injected into form fields. The injected payload persists in the system and executes when users view pages containing the compromised 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 installed AEM versionAccess the AEM Web Console (system/console/about) or check the version.properties file in the crx-quickstart folder. Look for the exact version number such as 6.5.x or 2024.x release.Affected if The installed version is lower than 6.5.21 or lower than 2024.5, meaning it falls within the affected version ranges.
-
Identify form fields accepting user inputReview the AEM Forms implementation and identify Adaptive Forms, Core Components with form fields, or custom form implementations that accept user-submitted data.Affected if The environment contains any form fields where users can submit data, as these are the injection points for stored XSS payloads.
-
Inspect form data storage for malicious scriptsQuery the JCR (Java Content Repository) at /content/forms/af or related form data paths using CRXDE Lite or a repository query. Search for common XSS patterns like <script>, javascript:, onerror=, and other HTML/script tags in stored form values.Affected if Any stored form data contains unsanitized script tags or event handlers that were injected into form fields.
-
Verify output encoding configurationCheck the Sling XSS API configuration in the AEM Web Console (system/console/config/com.adobe.granite.xss.impl) and review the XSS protection rules for form field output rendering.Affected if Output encoding is disabled or misconfigured, allowing stored scripts to execute when form fields are rendered to users.
A system is affected if it runs AEM versions below 6.5.21 or below 2024.5 AND contains form fields that accept user input without proper input validation and output encoding, allowing stored malicious scripts to persist and execute.
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 a version newer than 6.5.20, and implement robust input validation and output encoding for all form fields to prevent XSS attacks.
AEM 6.5.21 or later (6.5.x line); AEM 2024.5 or later (2024.x line)
- 1. Identify your current Adobe Experience Manager version by checking the product console or system information
- 2. If running AEM 6.5.x line: Upgrade to AEM 6.5.21 or later
- 3. If running AEM 2024.x line: Upgrade to 2024.5 or later
- 4. After upgrading, verify the patch was applied by confirming the new version in the system console
- 5. Test the fix by attempting to submit XSS payloads in form fields that were previously vulnerable
- 6. Clear browser cache and AEM instance cache after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36232 — 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-36232 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