CVE-2024-36147
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 into form inputs which persists on the server and executes when legitimate 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.
-
Determine installed AEM versionAccess the AEM System Information console or check the version.properties file in the AEM installation directory. On AEM as a Cloud Service, check the Cloud Manager environment details.Affected if The installed version is 6.5.20 or earlier, or the version is earlier than the 2024.5 release.
-
Identify active forms using form fieldsReview the AEM Forms or Core Components configuration to enumerate form models and their associated input fields. Check the content repository under /content for form pages or adaptive forms.Affected if Any form components that accept user input are present and enabled on the AEM instance.
-
Inspect stored form submissions for injected scriptsQuery the AEM content repository for existing form submission data. Examine stored values in form fields for suspicious patterns such as <script>, javascript:, onload, or other HTML/script tags. Use CRX/DE Lite or the Query Builder to search form submission nodes.Affected if Any form submission contains unsanitized HTML or JavaScript code that was injected into form input fields.
-
Verify if forms render user-supplied content without encodingReview the form field component configuration and any associated data display components. Check if the form's display logic or template escapes user input when rendering stored values back to users.Affected if Form fields render stored values using raw output or without proper context-aware encoding.
A user is affected if their AEM version is earlier than 6.5.21 or 2024.5, they have active forms accepting user input, and any form submissions contain malicious script payloads that would execute when viewed by other users.
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
Apply Adobe's security update by upgrading to AEM 6.5.21 or later. After patching, audit existing form submissions for any injected malicious scripts that may have been stored prior to the update.
6.5.21 (for 6.5.x branch) or 2024.5 (for 2024.x branch)
- 1. Identify your current Adobe Experience Manager version by checking the product information in the AEM Console or system/console/bundles
- 2. If running AEM 6.5.x line, plan upgrade to version 6.5.21 or later
- 3. If running AEM 2024.x line, plan upgrade to version 2024.5 or later
- 4. Review Adobe's official upgrade documentation and release notes for your target version
- 5. Create a backup of your current AEM instance including content, configurations, and custom code
- 6. Test the upgrade in a staging/development environment before production deployment
- 7. Execute the upgrade following Adobe's recommended upgrade procedure
- 8. After upgrade, verify that all custom applications and integrations function correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-36147 — 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-36147 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