CVE-2025-64791
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 vulnerable form fields. The malicious payload is stored in the system and executes when other users view pages containing the affected 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 versionAccess the AEM System Information console at /system/console/systeminfo 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 exactly 6.5.Affected if The installed version is 6.5.x where x is 23 or lower, or the version is below 2025.12.0 and not explicitly 6.5.x.
-
Identify if AEM Forms or custom form components are in useReview the AEM content structure for form-related components under /apps or /content where form fields accept user input. Check for components such as form text fields, textareas, or other input elements that store user-supplied data.Affected if Form components that accept and store user input are present and accessible to low-privileged users.
-
Verify XSS protection configurationAccess the AEM XSSAPI configuration via the Granite Operations Console at /system/console/configManager or check the XSS filter settings. Verify whether XSS filtering is enabled and configured to sanitize form field inputs.Affected if XSS protection is disabled, not configured, or set to allow unencoded HTML/script content in form fields.
-
Audit recent form submissions for malicious payloadsQuery the AEM repository for recent form submission content under /content/forms or custom form submission nodes. Look for common XSS patterns such as <script>, javascript:, onerror=, or other HTML/script injection attempts in form data.Affected if Form submission data contains unsanitized script tags or event handlers that would execute when rendered.
Your environment is affected if AEM version is below 6.5.24.0 or below 2025.12.0, and your instance uses form components that accept user input without proper XSS filtering 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
Implement proper input validation and output encoding on all form fields; enable and configure AEM's built-in XSS protection mechanisms to sanitize user-supplied content before rendering.
Adobe Experience Manager 6.5.24.0 or later (or 2025.12.0 or later for the 2025 release track)
- Verify current Adobe Experience Manager version by navigating to /system/console/bundles or checking the About Adobe Experience Manager page
- Review the AEM upgrade documentation at helpx.adobe.com for your specific version upgrade path
- Create a full backup of the AEM instance including the repository, database, and configuration files
- Stop the AEM instance before beginning the upgrade process
- Download Adobe Experience Manager 6.5.24.0 or later from the official Adobe distribution portal
- Run the upgrade installer following Adobe's standard upgrade procedure: java -jar aem-quickstart-6.5.24.0.jar
- After upgrade completes, verify the new version by checking /system/console/bundles shows 6.5.24.0
- Test critical form functionality to confirm the XSS fix is working and no regression exists
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64791 — 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-64791 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