dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64845

MEDIUM · 5.4 CVSS v3.1 Published 2025-12-10
Fix available
A fix is available. Upgrade to 6.5.24.0 / 2025.12.0 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Adobe 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 confidence

A stored (persistent) Cross-Site Scripting vulnerability in Adobe Experience Manager allows a low-privileged authenticated attacker to inject malicious JavaScript into form fields. The malicious payload persists and executes in victims' browsers when they view pages containing the affected form fields.

MitigationApply the vendor patch when available. In the interim, implement input validation and output encoding on affected form fields, and consider WAF rules to detect and block XSS payloads.

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
Experience ManagerApplication
Affected:< 6.5.24.0< 2025.12.0= 6.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed AEM version
    Access the AEM System Information console at /system/console/config or check the welcome page footer for the version number. Compare against the affected ranges: versions < 6.5.24.0, < 2025.12.0, or exactly version 6.5.
    Affected if The installed version falls within < 6.5.24.0, < 2025.12.0, or equals 6.5
  2. Verify AEM Forms functionality is in use
    Navigate to the Forms section in AEM Assets or Sites console. Check whether adaptive forms, foundation forms, or custom form components are created and published.
    Affected if Forms functionality is enabled and forms are actively used in the environment
  3. Identify low-privileged authenticated users
    Access the AEM User Administration console at /useradmin. Review users assigned to groups with limited permissions (such as authors, contributors, or custom low-privilege groups) who have access to form editing capabilities.
    Affected if Low-privileged authenticated users exist with ability to create or edit form content
  4. Inspect form field configurations for input validation
    Open form models or form containers in AEM Forms. Examine the XML schema or rule editor for individual form fields. Check whether input validation patterns and output encoding settings are configured.
    Affected if Form fields lack input validation rules or output encoding is disabled
  5. Search for suspicious payloads in form data
    Use CRXDE Lite (accessible at /crx/de) or the Query Builder to search nodes under /content/forms for stored values containing script tags, javascript:, or onerror/onload event handlers.
    Affected if Form data storage nodes contain encoded or raw XSS payloads such as <script> tags or event handler attributes

A user is affected if their AEM version is below 6.5.24.0 or below 2025.12.0 (or exactly 6.5), Forms are in use, and form fields lack proper input validation allowing stored XSS payloads to persist.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.5.24.0 / 2025.12.0 or later
Fixed in 6.5.24.02025.12.0
Interim mitigation

Apply the vendor patch when available. In the interim, implement input validation and output encoding on affected form fields, and consider WAF rules to detect and block XSS payloads.

Recommended fix High confidence

6.5.24.0 (or 2025.12.0 for the newer release line)

  1. Upgrade Adobe Experience Manager 6.5.x to version 6.5.24.0 or later
  2. If using the newer Experience Manager release (2025.x line), upgrade to version 2025.12.0 or later
  3. After upgrading, verify the fix by testing the form fields that were previously vulnerable to stored XSS
  4. Consult Adobe's release notes for the specific version you are upgrading to for any additional migration steps
Caveat Review Adobe's release notes for 6.5.24.0 to check for breaking changes or migration requirements specific to your current version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64845 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64845 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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