CVE-2025-64606
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 vulnerability in form fields. A low-privileged attacker can inject malicious JavaScript into form inputs, which persists on the page and executes in victim browsers when they view the affected content.
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.
-
Verify AEM product versionAccess the AEM System Information console (typically at /system/console/configMgr or via the Help menu > System Information) and locate the 'Adobe Experience Manager' version field. Alternatively, check the version.properties file in the crx-quickstart folder or run the version command via the AEM SDK.Affected if The installed version is any of: 6.5.x (where x is any number including 0), < 6.5.24.0, or < 2025.12.0 (including cloud versions before 2025.12.0). The version equals 6.5 without a decimal version number also indicates an affected release.
-
Identify Forms or Adaptive Forms usageCheck if the AEM Forms addon is installed by navigating to Tools > Operations > Web Console and searching for 'Forms' or 'Adaptive Form' bundles. Also check for the presence of /content/forms/af or similar form-related content paths in the AEM repository via CRXDE Lite.Affected if AEM Forms or Adaptive Forms modules are installed and active. The vulnerability exists in form field components specifically within the Forms functionality.
-
Confirm form authoring is accessible to low-privilege usersReview user group permissions in AEM by navigating to Tools > Security > Groups or Users. Check if non-admin users have access to form authoring features such as editing Adaptive Forms or modifying form field properties. Look for groups like 'form-authors' or similar with permissions to /content/forms/.Affected if Users with low-privileged accounts (non-admin, content-author level) have permission to create or edit form content and save changes to the repository.
-
Inspect form field input configurationsOpen CRXDE Lite (at /crx/de) and navigate to a sample form's component definition under /libs/fd/af/components or /apps/fd/af/components. Examine the field components (such as text input, textarea, or number fields) to see if input validation or output encoding is explicitly configured.Affected if Form field components do not have explicit input validation rules or server-side output encoding configured, allowing arbitrary JavaScript to be stored in field values.
You are affected if your AEM version is 6.5.x, < 6.5.24.0, or < 2025.12.0, AND you have AEM Forms/Adaptive Forms enabled with low-privileged users able to author form content without sanitization.
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 AEM to a version newer than 6.5.23. Implement output encoding and input validation on form fields, and consider Content Security Policy headers to mitigate XSS execution.
AEM 6.5.24.0 or later (6.5.x branch); or AEM 2025.12.0 or later (cloud/continuous release)
- Backup the current AEM instance including repository, database, and configuration files
- Review the Adobe Experience Manager 6.5.24.0 upgrade documentation or 2025.12.0 release notes for any pre-upgrade requirements
- Download Adobe Experience Manager 6.5.24.0 (for 6.5.x branch) or 2025.12.0 (for cloud/continuous release) from the official Adobe distribution portal
- Stop the running AEM instance
- Install the upgraded version following Adobe's standard upgrade procedures
- After installation, verify the AEM instance starts successfully
- Test that the stored XSS vulnerability is no longer exploitable in the affected form fields
- Validate that all critical workflows and custom applications function correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64606 — 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-64606 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