CVE-2025-64626
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 XSS vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious payload persists on the server and executes 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.
-
Determine installed AEM versionAccess the AEM System Information console or Help > About Adobe Experience Manager page to retrieve the exact product version numberAffected if The installed version is 6.5.x where x is less than 24, or any version earlier than 2025.12.0
-
Identify AEM forms in useReview the AEM Forms module or Forms & Documents section to enumerate any adaptive forms, core components forms, or custom form implementations deployed in the environmentAffected if Any form functionality is enabled or deployed in the AEM instance
-
Inspect form field data storageQuery the AEM content repository (via CRXDE Lite or repository browser) under /content/forms or similar paths where form submission data is stored, examining stored values in form field nodesAffected if Stored form data contains unsanitized HTML or JavaScript payloads that could execute in a browser
-
Review recent form submission audit logsAccess AEM audit logs or form submission records to identify any submissions containing script tags, javascript: protocols, or event handler attributes (onerror, onload, onclick)Affected if Audit logs reveal form submissions with suspicious payload patterns typical of XSS attempts
You are affected if your AEM version is 6.5.23 or earlier, or any version below 2025.12.0, and your environment has forms that accept user input which is stored and later rendered without proper output encoding.
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. Additionally, implement input validation and output encoding on form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.24.0 or later, or 2025.12.0 or later release train
- Back up your current Adobe Experience Manager instance and database before proceeding with any upgrade
- Review the official Adobe Experience Manager upgrade documentation at helpx.adobe.com for your specific version
- Test the upgrade in a non-production/staging environment first
- Upgrade Adobe Experience Manager to version 6.5.24.0 or later (or to version 2025.12.0 or later if using the newer release train)
- After upgrade, verify that the stored XSS vulnerability is remediated by testing the affected form fields
- Deploy the upgraded instance to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64626 — 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-64626 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