CVE-2024-36152
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 that allows attackers to inject malicious JavaScript into form fields. When victims browse to pages containing the compromised form fields, the injected scripts execute 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.
-
Identify AEM installation and versionAccess the AEM welcome page (typically at /libs/granite/core/content/login.html or /welcome.html) or check the version.properties file in the crx-quickstart folder. You can also query the System Information console at /system/console/bundles or /system/console/productinfo.Affected if The displayed version is 6.5.20 or earlier, or the version starts with a year earlier than 2024.5 (e.g., 2024.0, 2024.1, 2024.2, 2024.3, or 2024.4).
-
Identify forms that accept user inputReview the AEM content structure under /content for pages containing form components (look for nodes with sling:resourceType containing 'form'). Check the Granite UI Form components under /libs/granite/ui/components/foundation/form or custom form implementations in /apps.Affected if AEM contains custom or extended form components that accept user-submitted text input without explicit server-side validation rules configured.
You are affected if your AEM version is below 6.5.21 or below 2024.5 AND you have form components that accept user input which may not have proper input sanitization configured.
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 receive the security patch. Alternatively, apply Adobe's security hotfix if available, and implement input validation/sanitization on affected form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.21 or later, or AEM 2024.5 or later
- 1. Back up the current Adobe Experience Manager instance and all content repositories before proceeding
- 2. Review the official Adobe release notes for version 6.5.21 (or 2024.5 for the newer release line) to understand any changes
- 3. Test the upgrade in a non-production/staging environment first
- 4. Apply the upgrade to the production environment following Adobe's official AEM upgrade documentation
- 5. Verify the fix by checking that malicious scripts can no longer be injected into form fields
- 6. Clear AEM caches and rebuild any search indexes if recommended in the release notes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36152 — 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-36152 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