CVE-2025-64607
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 confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege attacker can inject malicious JavaScript that executes in victim browsers when they view pages containing the compromised form 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.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.
-
Identify the installed Adobe Experience Manager versionAccess the AEM Welcome page at /libs/granite/core/content/login.html or check the system information at /system/console/configMgr/org.apache.sling.jcr.davex.impl.servlets.SlingDavExServlet - the version is displayed on the Welcome page footer or in the product info sectionAffected if The installed version is 6.5.23 or earlier, or exactly 6.5, or any version lower than 6.5.24.0 or 2025.12.0
-
Determine if AEM Forms module is deployedNavigate to /libs/fd/fm/view/templates/global - if this path exists and returns content, the Forms module is installed. Alternatively, check /libs/forms for form-related componentsAffected if The Forms module is present and accessible, as the XSS vulnerability exists in form fields
-
Review custom form field configurations in CRX/DEOpen CRX/DE at /crx/de/index.jsp and navigate to /apps or /content where custom form components are stored. Inspect form field node properties under /apps/*/components and /content/*/forms for any suspicious script tags or event handler attributes in field definitionsAffected if Custom form field components exist in the repository with unsanitized attribute values
-
Audit form submission data in the repositoryQuery the JCR repository using the Query tool in CRX/DE or AEM Developer Mode. Search for form container nodes under /content/forms/af and inspect the value nodes for any stored script tags, javascript: URIs, or event handler attributes like onload, onerror, onclickAffected if Form submission data contains unencoded script tags or event handler attributes in user-controllable fields
-
Inspect the XSS filter configurationNavigate to /system/console/configMgr and locate the XSS filter configuration (com.adobe.granite.xss). Verify whether form field attributes are listed in the allowed attributes or if the XSS protection is bypassed for form componentsAffected if XSS filter is disabled or form field attributes are not in the exclusion list for the affected form components
The environment is affected if AEM version is 6.5.23 or earlier, 6.5, or below 6.5.24.0/2025.12.0 AND the Forms module is in use with user-generated form field content that could contain malicious scripts.
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 a version beyond 6.5.23 as provided by Adobe's official security patch. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure.
6.5.24.0 or later (6.5.x line) or 2025.12.0 or later (cloud/latest)
- Review the Adobe Experience Manager upgrade documentation for your current version
- Plan and schedule the upgrade during a maintenance window
- Backup your current AEM instance including the repository, database, and configurations
- Test the upgrade in a staging environment before production deployment
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later for the 6.5.x line
- Verify the XSS vulnerability is patched by checking the Adobe security bulletin
- Validate that existing forms and custom components function correctly after upgrade
- Monitor for any post-upgrade issues in production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64607 — 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-64607 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