dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64596

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 in form fields. A low-privileged attacker can inject malicious JavaScript into vulnerable form inputs, which persists in the system and executes when other users view the affected pages.

MitigationUpgrade to AEM 6.5.24 or later, which contains the security fix. Until then, implement output encoding and input validation on affected form fields, and consider restricting low-privileged user permissions to form editing.

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. Identify installed AEM version
    Access the AEM System Information console at /system/console/status-productinfo or check the version from the AEM Start page footer. You can also check the JAR file name in the crx-quickstart folder.
    Affected if The version shown is 6.5.23 or earlier, or falls below 6.5.24.0, or is below 2025.12.0, or is exactly version 6.5.
  2. Confirm AEM deployment type
    Determine if the instance is using the 6.5 release line or the newer release cadence (2025.x). Check the product version string returned from the system information console.
    Affected if The deployment uses AEM 6.5.x with version 6.5.23 or earlier, or uses the 2025.x release line with version below 2025.12.0.
  3. Identify custom form field components
    Review the application codebase and look for custom form input components or custom templates that render form fields. Check the /apps folder in CRX/DE for custom form-related nodes under /apps/your-project/components.
    Affected if Custom form components or form-based AEM components are present in the system, as these could contain the vulnerable form fields.
  4. Assess low-privileged user access
    Check user group permissions in AEM via the User Administration console at /useradmin. Look for groups with limited permissions that have access to create or edit form content, such as the 'content-authors' group.
    Affected if Low-privileged users (non-admin) have write access to form editing capabilities or content pages containing forms.

You are affected if your AEM version is 6.5.23 or earlier, below 6.5.24.0, below 2025.12.0, or exactly 6.5, AND your system allows low-privileged users to edit form fields that other users will view.

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

Upgrade to AEM 6.5.24 or later, which contains the security fix. Until then, implement output encoding and input validation on affected form fields, and consider restricting low-privileged user permissions to form editing.

Recommended fix High confidence

AEM 6.5.24.0 or later (or AEM as a Cloud Service 2025.12.0+)

  1. Backup your Adobe Experience Manager instance and database before upgrading
  2. Review Adobe's upgrade documentation for AEM 6.5.24.0 to understand any migration requirements
  3. Test the upgrade in a non-production environment to ensure compatibility with custom code and integrations
  4. Upgrade AEM from version 6.5.23 or earlier to version 6.5.24.0 (or later 6.5.x release)
  5. If using AEM as a Cloud Service, upgrade to 2025.12.0 or later
  6. After upgrade, verify the XSS vulnerability is remediated by testing the affected form fields
  7. Deploy the tested upgrade to production
Caveat AEM major version upgrades may introduce breaking changes; custom code, integrations, and workflows should be tested for compatibility 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
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64596 — 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-64596 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