CVE-2025-64609
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 where low-privileged users can inject malicious JavaScript into form fields. When other users view pages containing these compromised fields, the injected script executes in their browsers, potentially allowing session hijacking or data theft.
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 Adobe Experience Manager versionNavigate to the AEM Welcome page or check the version file (crx-quickstart/etc/version.txt). In the AEM Web Console, go to Help > System Information to view the product version. Alternatively, query the JMX console or check the manifest file in the AEM installation directory.Affected if The installed version is lower than 6.5.24.0, lower than 2025.12.0, or exactly 6.5 (any patch level below 6.5.24.0).
-
Identify if AEM Forms is deployedCheck if the AEM Forms addon is installed by navigating to the AEM Forms UI (locally navigate to /aem/forms or check the package manager for AEM Forms packages). Look for form fragments, adaptive forms, or form data model components in the /content/forms folder.Affected if AEM Forms or any form-based components are present in the environment, as these provide the form fields where malicious script could be injected.
-
Review user group permissionsNavigate to the User Administration console (Tools > Security > Users or Tools > Security > Groups). Identify which users have access to create or edit form content. Check the permissions of the 'forms-user' or 'content-authors' group to see if low-privilege users can access form editing capabilities.Affected if Low-privilege users (non-admin) have permissions to create, edit, or submit forms that are rendered on published pages.
-
Inspect form field validation settingsIn AEM Forms author instance, open any adaptive form or form container. Check the Validation properties of text input fields. Look for the 'Allow Rich Text' or 'Allow HTML' options. Check the client-side and server-side validation patterns configured on form fields.Affected if Form fields lack input validation rules, output encoding is not enabled, or 'Allow HTML' is set to true for form input components.
You are affected if your AEM version is below 6.5.24.0 or below 2025.12.0, and your environment uses AEM Forms with low-privilege users able to inject unsanitized content into form fields that other users view.
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 a version newer than 6.5.23. Additionally, implement input validation and output encoding on all form fields to prevent XSS injection.
AEM 6.5.24.0 or later / 2025.12.0
- Review the Adobe Experience Manager release notes and upgrade documentation at helpx.adobe.com for version 6.5.24.0 or later
- Plan and schedule the upgrade in a non-production environment first
- Backup the current AEM instance including repository, database, and configurations
- Perform the upgrade to AEM 6.5.24.0 or later (or to 2025.12.0 if available)
- Verify the upgrade was successful and test critical workflows
- Deploy the updated version to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64609 — 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-64609 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