CVE-2025-64611
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-privileged authenticated attacker can inject malicious JavaScript payloads into form input fields, which are persisted in the system and execute in victim users' 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 installed AEM versionAccess the AEM System Information console at /system/console/status-productinfo or check the version.properties file in the installation directory. Alternatively, view the Welcome page which displays the version number.Affected if The version is 6.5.23 or earlier, or falls below 2025.12.0 (for the 2025 release track).
-
Confirm AEM Forms or form components are in useCheck the AEM instance for the presence of adaptive forms, core form components, or custom form fields under /content/forms in the repository. Query the repository at /bin/querybuilder.json?path=/content/forms&type=cq:Page to enumerate form content.Affected if Form structures exist in the content repository, indicating the feature where the XSS can be injected is present.
-
Inspect form field content for injected scriptsUsing CRX/DE Lite (accessible at /crx/de), navigate to /content/forms and examine form field nodes (typically under /fields or similar structures) for any script tags, javascript: URIs, or event handler attributes (onerror, onload, onClick) in field values.Affected if Any form field nodes contain script tags, JavaScript URIs, or HTML event handler attributes that were not authored by administrators.
The environment is affected if the installed AEM version is below 6.5.24.0 (or below 2025.12.0 for the newer release track) AND forms with user-editable input fields exist in the system where malicious scripts could have been injected.
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
Apply the security update by upgrading Adobe Experience Manager to version 6.5.24 or later to patch the stored XSS vulnerability in form fields.
AEM 6.5.24.0 or AEM 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 if using the newer release cadence
- After upgrade, verify the fix by testing form fields that could be used for XSS injection
- Review Adobe's release notes for the specific security fixes included in the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64611 — 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-64611 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