dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64615

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

Adobe Experience Manager versions 6.5.23 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability. A low-privilege attacker can inject malicious JavaScript into vulnerable form fields. When victims browse to pages containing these compromised fields, the injected scripts execute in their browsers, enabling session hijacking, credential theft, or other client-side attacks.

MitigationUpdate Adobe Experience Manager to a version later than 6.5.23 to obtain the vendor patch. Additionally, audit and sanitize existing form data in the system to remove any injected malicious scripts.

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. Check installed Adobe Experience Manager version
    Access the AEM Welcome page or navigate to System Information (typically at /system/console/systeminfo or via Help > System Information in the AEM UI). Locate the 'Adobe Experience Manager' version field.
    Affected if The version listed is 6.5.23 or earlier, or falls below 6.5.24.0, or is below 2025.12.0.
  2. Identify AEM Forms modules in use
    Review the AEM console for enabled Forms features. Navigate to Forms (if available in the left navigation) or check the package manager for installed Form-related packages. Look for Adaptive Forms, Core Components with form elements, or Foundation Forms.
    Affected if Forms modules are installed and active in the AEM instance.
  3. Verify low-privilege user access to form authoring
    Access the User Administration console (/security/users.html or /useradmin). Review permissions for standard or low-privilege users. Check if these users have create, modify, or contributor permissions on content pages containing form components.
    Affected if Low-privilege users have permissions to create or edit content containing form fields.
  4. Inspect form content for unexpected script content
    Use AEM Query Builder or CRX/DE Lite (at /crx/de) to search form component nodes. Look in content repositories under /content for nodes containing form fields. Inspect the 'value' or 'text' properties of form components for script tags, javascript: URIs, or HTML event attributes.
    Affected if Any form field data contains injected script tags, javascript: protocols, or event handler attributes that were not authored by administrators.

You are affected if your AEM version is below 6.5.24.0 or below 2025.12.0 AND your environment has Forms enabled with low-privilege user access, or if malicious script content is already present in form data.

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

Update Adobe Experience Manager to a version later than 6.5.23 to obtain the vendor patch. Additionally, audit and sanitize existing form data in the system to remove any injected malicious scripts.

Recommended fix High confidence

Adobe Experience Manager 6.5.24.0 or later / 2025.12.0 or later

  1. Backup the current Adobe Experience Manager instance and all content repositories
  2. Review the Adobe Experience Manager upgrade documentation for version 6.5.24.0 or 2025.12.0
  3. Ensure compatibility of custom code and third-party integrations with the target version
  4. Upgrade Adobe Experience Manager to version 6.5.24.0 or later, or to version 2025.12.0 or later
  5. After upgrade, verify that the XSS vulnerability is patched by testing the previously vulnerable form fields
  6. Validate that all AEM functionalities and workflows operate correctly post-upgrade
Caveat Standard AEM upgrade considerations apply - review breaking changes in release notes and test custom integrations before production deployment

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-64615 — 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-64615 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