CVE-2025-64793
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 · moderate confidenceAdobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. Low-privileged authenticated users can inject malicious JavaScript into form fields, which persists in the system. When other users view pages containing these compromised form fields, the malicious 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.
-
Check installed AEM versionNavigate to AEM Welcome page > Help > Version, or check the version.properties file in the crx-quickstart folder, or query the system console at /system/console/status ProductInfo to retrieve the exact installed version numberAffected if The version is 6.5.23 or earlier, or equals 6.5, or is 2025.12.0 (any version before 6.5.24.0 or before 2025.12.0 for the 2025 track)
-
Verify Forms or Adaptive Forms feature is enabledCheck if AEM Forms or Adaptive Forms component is installed and enabled by navigating to AEM Granite UI Forms or checking the package manager for forms-related packagesAffected if Forms or Adaptive Forms components are installed and accessible to users
-
Identify low-privileged user access to form editingReview user group permissions in AEM Tools > Security > Permissions, specifically checking if users with low-privilege roles (such as content-authors or users without admin rights) have create or edit permissions on form-related content paths under /content/formsAffected if Low-privileged authenticated users have permission to create or edit form fields
-
Audit existing form submissions for malicious contentSearch the AEM repository (using CRXDE Lite or Query Builder) under /content/forms for stored script tags, script elements, or JavaScript event handlers in form field data values, or review form submission data in the Granite CQ Forms containerAffected if Form fields contain unsanitized script tags, onclick/onload handlers, or JavaScript code that could execute in other users' browsers
You are affected if your AEM version is below 6.5.24.0 or below 2025.12.0, Forms feature is enabled, low-privileged users can access form fields, and any existing form data contains malicious script content.
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 Adobe's official patch by upgrading to AEM 6.5.24 or later. Before deployment, audit all user-generated form fields for existing malicious content and implement output encoding on form field rendering.
Adobe Experience Manager 6.5.24.0 or later, or 2025.12.0 or later
- Create a complete backup of the AEM repository (crx-quickstart) and database before starting the upgrade
- Review Adobe Experience Manager Upgrade Documentation for the target version to understand any specific migration requirements
- Test the upgrade in a non-production environment first to identify potential issues
- Stop the AEM instance gracefully before beginning the upgrade process
- Install Adobe Experience Manager 6.5.24.0 or later (or 2025.12.0 or later for the 2025 release track)
- After upgrade, verify that the AEM instance starts successfully and all bundles are in active state
- Clear browser cache and test the previously vulnerable form fields to confirm the XSS vulnerability is remediated
- Review the Adobe security bulletin for any post-upgrade configuration recommendations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64793 — 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-64793 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