CVE-2025-64817
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. The malicious payload persists in the system and executes in victims' browsers when they view pages containing the compromised 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 the installed Adobe Experience Manager versionAccess the AEM System Information console at /system/console/systeminfo or check the welcome page for version detailsAffected if The version displayed is 6.5.23 or earlier, or falls below 6.5.24.0, or is below 2025.12.0, or shows only 6.5 without a specific patch version
-
Identify forms accessible to low-privileged usersReview the user permissions for groups assigned to low-privileged accounts and identify which form components or adaptive forms they can access or editAffected if Low-privileged users have write or contributor access to any form fields in the system
-
Inspect form field content for malicious payloadsQuery the content repository or examine form field data stored in the system for unexpected script tags, event handlers, or JavaScript patterns (such as <script>, onload=, onerror=, javascript:); use CRXDE Lite or content search to review stored form dataAffected if Any form field contains persisted script injection payloads or unusual HTML/JavaScript content that was not intentionally authored
-
Verify if rendered form pages execute injected scriptsAccess pages containing forms as a standard user and view the page source or use browser developer tools to inspect if stored form data renders as executable JavaScriptAffected if Injected payloads execute in the browser when viewing pages with compromised form fields
You are affected if your AEM version is below 6.5.24.0 or 2025.12.0 AND low-privileged users can access form fields where malicious scripts could be injected and persisted.
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
Update Adobe Experience Manager to version 6.5.24 or later to patch the vulnerability. Additionally, implement output encoding and input validation on all form fields as a defense-in-depth measure.
Adobe Experience Manager 6.5.24.0 or later (6.5.x line), or 2025.12.0 or later
- Review the Adobe Experience Manager upgrade documentation for your current version
- Test the upgrade in a non-production environment before deploying
- Ensure all custom code and third-party integrations are compatible with the target version
- Create a full backup of your AEM instance including repository, database, and configurations
- Upgrade to Adobe Experience Manager 6.5.24.0 or later for the 6.5.x release line, OR upgrade to 2025.12.0 or later for the newer release train
- Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager page
- Test the previously vulnerable form fields to confirm the XSS vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64817 — 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-64817 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