CVE-2025-64605
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 attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes in victim users' 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.
-
Check Adobe Experience Manager versionLocate the AEM version number in the product about page (navigate to Help > About Adobe Experience Manager) or check the version.properties file in the crx-quickstart directory. Compare the installed version against the affected ranges: versions below 6.5.24.0, versions below 2025.12.0, or any 6.5.x release.Affected if The installed version is 6.5.x, < 6.5.24.0, or < 2025.12.0
-
Identify form fields that accept user inputReview the AEM Forms implementation and custom form components in the system. Document all form fields that allow user-generated content to be submitted and stored, including text inputs, textareas, and similar input types.Affected if Custom or out-of-the-box form fields exist that accept and store user input without explicit validation constraints
-
Verify input validation on form fieldsInspect the form field configurations and any associated validation rules in the AEM Forms or Core Components framework. Check whether validation patterns or constraints are defined for each input field.Affected if Form fields lack input validation rules or allow unrestricted text input that could contain script tags or event handlers
-
Confirm output encoding is appliedReview the form field rendering templates and any custom components that display stored form data. Check whether the templates use AEM's built-in encoding utilities (such as XSS API or ESAPI encoding) when rendering user-submitted content.Affected if Stored form data is rendered without proper output encoding, allowing raw user input to be displayed in pages
-
Inspect stored form data for suspicious contentQuery the AEM repository (via CRXDE Lite or the Query Builder) for any form submission data that contains script tags, javascript: URIs, or event handler attributes (onclick, onerror, etc.) in text fields.Affected if Malicious scripts or event handlers are found stored in form field content within the repository
Your environment is affected if you run AEM versions below 6.5.24.0 or below 2025.12.0, and you have form fields that accept user input without proper input validation and 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 to obtain the security patch. Alternatively, implement strict input validation and output encoding on form fields, and deploy Content Security Policy headers to mitigate XSS execution.
Adobe Experience Manager 6.5.24.0 (or later for 6.5.x line) or 2025.12.0 (or later for 2025.x line)
- 1. Identify the current Adobe Experience Manager version in use (check /system/console or version.properties)
- 2. For AEM 6.5.x users: Plan upgrade to version 6.5.24.0 or later
- 3. For AEM 2025.x users: Plan upgrade to version 2025.12.0 or later
- 4. Create a full backup of the current AEM instance including repository, database, and configurations
- 5. Test the upgrade in a non-production environment first
- 6. Apply the upgrade following Adobe's standard upgrade documentation
- 7. Verify the patch is applied by checking the AEM version after upgrade
- 8. Validate that the form fields previously vulnerable to XSS are now properly sanitizing input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $11,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64605 — 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-64605 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