CVE-2025-64612
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 authenticated attacker can inject malicious JavaScript payloads into vulnerable form input fields. When other users (including administrators) browse to pages containing these compromised form fields, the stored malicious script executes in their browsers, potentially enabling session hijacking, credential theft, or further privilege escalation.
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 AEM version is vulnerableCheck the installed Adobe Experience Manager version. This is typically visible in the AEM Systems Information console at /system/console/systeminfo, or by locating the version.properties file in the crx-quickstart directory. Compare the version number against the affected ranges: versions < 6.5.24.0, < 2025.12.0, or 6.5.x versions 6.5.23 and earlier.Affected if The installed version is 6.5.23 or earlier, or any version below 6.5.24.0 or 2025.12.0.
-
Identify deployed form componentsReview the AEM instance for any custom form components or adaptive forms. Check the /apps or /content directories for nodes containing form-related components such as form, textfield, textarea, or numberinput components. Use CRXDE Lite or the Package Manager to inventory form-related content packages.Affected if Custom or adaptive form components are installed and the AEM version falls within the affected range.
-
Inspect form field content for malicious scriptsQuery the repository for stored scripts in form field data. Use CRXDE Lite or a repository query to search form component nodes under /content for suspicious patterns such as <script>, javascript:, onload=, onerror=, or other XSS vectors in field values. Review recent content updates in the form field nodes.Affected if Malicious JavaScript payloads are found stored in form field data nodes.
-
Review form submission logsExamine AEM request logs and form submission audit logs for patterns indicating XSS injection attempts. Look for form POST requests containing script tags or event handlers in input parameters. Check logs in the crx-quickstart/logs directory for unusual form submissions.Affected if Logs show recent form submissions containing XSS payload patterns.
The environment is affected if the installed AEM version is 6.5.23 or earlier, or any version below 6.5.24.0 or 2025.12.0, and custom form components are in use.
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 the vendor patch by upgrading to Adobe Experience Manager version 6.5.24 or later. Additionally, implement Content Security Policy (CSP) headers and ensure all custom form components properly sanitize user input using output encoding.
AEM 6.5.24.0 (for 6.5.x line) or 2025.12.0 (for newer release cadence)
- 1. Identify current Adobe Experience Manager version by checking the product information in the AEM System Overview or through the version.properties file
- 2. For AEM 6.5.x line: Plan upgrade to version 6.5.24.0 or later
- 3. For AEM newer release cadence: Plan upgrade to version 2025.12.0 or later
- 4. Review Adobe's official upgrade documentation for AEM 6.5.24.0 or the 2025.12.0 release
- 5. Create a full backup of the current AEM instance including content, configurations, and custom code
- 6. Test the upgrade in a non-production environment to verify compatibility with custom code and integrations
- 7. Execute the upgrade following Adobe's recommended procedures
- 8. After upgrade, verify the XSS vulnerability is remediated by attempting to inject script content into the previously affected form fields
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-64612 — 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-64612 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