CVE-2025-64847
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.23 and earlier are affected by a stored Cross-Site Scripting (XSS) vulnerability that could be abused by a low privileged 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 confidenceStored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into 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.24.0< 2025.12.0= 6.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 Adobe Experience Manager product versionNavigate to the AEM welcome page or access /system/console/configMgr, or use the CRXDE Lite interface to locate the version information typically found in the 'com.adobe.granite.platform' bundle or in the 'version.properties' file in the installation directoryAffected if The installed version is 6.5.x where x is 23 or lower, or the version displays as 2025.12.0 or earlier (prior to the 6.5.24.0 or 2025.12.0 patches)
-
Identify Adaptive Forms or custom form components in useNavigate to the Forms section in AEM Assets or Authoring interface and list all Adaptive Forms or custom form components that exist in the /content/forms folder or similar form storage locationsAffected if Any Adaptive Forms or custom form components are present and accessible to low-privileged users for editing or content authoring
-
Verify low-privileged user access to form editingLog in with a low-privilege user account (such as a standard 'user' or 'author' role without admin rights) and attempt to access and edit form components or create new form submissions in the Forms sectionAffected if Low-privilege users can create, edit, or submit forms without elevated permissions
-
Inspect form field content for injected scriptsUsing CRXDE Lite, navigate to the form content nodes (typically under /content/forms or /content/dam/forms) and inspect the jcr:content or submitted data nodes for any <script> tags, javascript: URIs, or on* event handlers in field valuesAffected if Any form field content nodes contain malicious script injections that would execute when users view the affected pages
A user is affected if their AEM version is below 6.5.24.0 or 2025.12.0 AND they have Adaptive Forms or custom form components accessible to low-privileged users on their site.
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.24.02025.12.0
Upgrade Adobe Experience Manager to version 6.5.24 or later to remediate this vulnerability.
Adobe Experience Manager 6.5.24.0 or later / 2025.12.0 or later
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later
- Alternatively, upgrade to version 2025.12.0 or later
- After upgrading, verify the fix by testing form fields that were previously vulnerable to XSS
- Ensure the upgraded version is deployed across all environments (development, staging, production)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64847 — 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-2025-64847 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