CVE-2024-36175
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 that persists in the form data and executes in victim browsers when they view pages containing the affected 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.
-
Determine installed AEM versionNavigate to AEM Welcome page > Tools > Operations > Diagnosis, or access /system/console/systeminfo to view the version. Also check the JAR file manifest or the version file in crx-quickstart/app.Affected if The version is earlier than 6.5.21 (for 6.x releases) or earlier than 2024.5 (for Cloud/2024 releases)
-
Identify if AEM Forms is enabledCheck if the Forms add-on package is installed by reviewing installed packages in Package Manager (/crx/packmgr) or by checking for the presence of the /libs/fd path in the repository.Affected if Forms or adaptive forms functionality is installed and active, as the XSS vulnerability exists in form field handling
-
Review custom form component usageSearch the repository under /apps for custom form components or adaptive form configurations that accept user input. Use CRXDE Lite (/crx/de) or query the repository for components under /apps that extend form field components.Affected if Custom or out-of-the-box form components that store user-submitted data are in use on published pages
-
Inspect form data storage for unencoded contentExamine stored form data in the repository (under /content/usergenerated or custom form submission paths) using CRXDE Lite. Check if form submission data is stored without visible evidence of input validation or encoding being applied during submission.Affected if Form submissions are stored and can be viewed on pages accessible to other users without server-side output encoding
You are affected if your AEM version is below 6.5.21 (6.x line) or below 2024.5, and you have AEM Forms or form-based components enabled that accept and display 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
Update to AEM 6.5.21 or later to obtain the security patch. Additionally, implement input validation and output encoding on all form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.21 (on-prem) or 2024.5 (cloud)
- Upgrade Adobe Experience Manager 6.5.x installations to version 6.5.21 or later
- Alternatively, upgrade Adobe Experience Manager cloud installations to version 2024.5 or later
- After upgrading, verify the XSS vulnerability is resolved by testing form fields that could accept user input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36175 — 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-36175 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