CVE-2025-64796
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 victims browse to pages containing these compromised fields, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or defacement.
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 Welcome page or navigate to /system/console/configMgr and locate the 'Adobe Experience Manager Web Console' or check the 'com.adobe.granite.packaging.internal' bundle for version info. Alternatively, check the crx-quickstart/doc/cq.pdf file or run 'java -jar cq-quickstart-*.jar -version' if accessible.Affected if The installed version is 6.5.23 or earlier, equals 6.5 specifically, or is below 2025.12.0
-
Confirm AEM edition and deployment typeVerify the deployment is Adobe Experience Manager (not Adobe Campaign or other Adobe products). Check the product name displayed in the AEM Welcome page header or the About Adobe Experience Manager section (Help > About).Affected if The deployment is Adobe Experience Manager in any supported edition (Communities, Forms, Assets, Sites, etc.) matching the version conditions in step 1
-
Identify active form functionalitiesReview the AEM instance for enabled form components. Check /libs/fd/fm, /libs/foundation/components, or custom form paths in CRXDE Lite (navigate to /apps and look for 'form' or 'fd' nodes). Look for Adaptive Forms, Foundation Forms, or custom form models.Affected if The instance has Forms (AEM Forms), Foundation Form components, or any custom form fields enabled and accessible to users
-
Assess low-privilege user access to form editingIn AEM Tools (Tools > Security > Permissions), verify if users with 'contributor' or 'editor' roles (non-admin) have access to create or edit form content. Check content paths under /content for writable form nodes accessible to these users.Affected if Low-privilege users (non-admin) have write access to form fields or form content nodes in the repository
-
Audit existing form field configurationsIn CRXDE Lite, examine form field nodes under /content for missing 'xssProtect' or 'escape' attributes. Check if form field components use the XSS API (com.adobe.granite.xss) for output encoding. Look for form field nodes in adaptive forms or foundation form components.Affected if Form fields exist without proper XSS protection attributes or do not leverage AEM's XSS protection APIs for output encoding
The environment is affected if running any AEM version below 6.5.24.0 or below 2025.12.0, and the instance has form fields accessible to low-privilege users without proper XSS protection enabled.
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 AEM version 6.5.24 or later which contains the security patch, or implement strict input validation and output encoding on all form fields using AEM's built-in XSS protection APIs.
Adobe Experience Manager 6.5.24.0 or later (or AEM 2025.12.0 and later for the cloud release line)
- Backup the current AEM instance and repository before starting the upgrade process
- Review Adobe Experience Manager 6.5.24.0 release notes and upgrade documentation at helpx.adobe.com for any specific migration requirements
- Ensure the target environment meets the minimum requirements for AEM 6.5.24.0
- Stop the AEM instance and any related services
- Upgrade AEM from the current version to 6.5.24.0 (or the latest 6.5.x release available) using the Adobe Package Manager or upgrade procedure
- After upgrade, verify that the form fields mentioned in the vulnerability are now properly sanitizing input
- Test the application to confirm legitimate form submissions still function correctly
- Clear AEM caches and rebuild any custom indexes if required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64796 — 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-64796 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