dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-64593

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

Stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.23 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The malicious script persists in the system and executes in victims' browsers when they view pages containing the compromised form fields.

MitigationUpgrade to a patched version of Adobe Experience Manager (6.5.24 or later) and implement input validation/sanitization on all form fields to prevent script injection.

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 the installed AEM version
    Access the AEM System Information console at /system/console/status-productinfo or check the crx-quickstart/README.txt file. Alternatively, navigate to Help > About Adobe Experience Manager in the AEM welcome screen.
    Affected if The installed version is 6.5.23 or earlier, or falls below 2025.12.0 (for the 2025 release track)
  2. Confirm the Forms module is in use
    Check if the AEM Forms add-on is installed by navigating to /libs/fd/fm Libraray check or look for the Forms menu in the AEM navigation. Also verify if any form containers exist under /content/forms/af in the CRX/DE repository.
    Affected if Forms are enabled and users can create or edit form fields
  3. Verify low-privileged user access to forms
    Review the permission matrix for users with minimal privileges (such as those assigned the 'content-author' or 'forms-user' group). Confirm whether these users have write access to form authoring consoles at /aem/forms or through the Forms UI.
    Affected if Low-privileged users can access form creation or editing interfaces
  4. Inspect stored form data for suspicious content
    In CRX/DE Lite (accessible at /crx/de), navigate to /content/forms/af and examine the XML or JCR nodes storing form field values. Look for unescaped HTML script tags, javascript: URIs, or event handlers in text fields.
    Affected if Any form field nodes contain raw script tags or javascript: prefixes in their values

You are affected if your AEM version is below 6.5.24.0 (or below 2025.12.0 for the 2025 release), Forms are enabled, and low-privileged users can inject content into form fields that may contain malicious scripts.

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 a patched version of Adobe Experience Manager (6.5.24 or later) and implement input validation/sanitization on all form fields to prevent script injection.

Recommended fix High confidence

AEM 6.5.24.0 or later (6.5.x branch); or AEM 2025.12.0 or later (newer release cadence)

  1. 1. Identify current Adobe Experience Manager version by navigating to System Overview in the AEM welcome page or checking the version.properties file
  2. 2. Confirm the installed version is affected: < 6.5.24.0 for the 6.5.x branch, or < 2025.12.0 for the 2024+ release cadence versions
  3. 3. Review Adobe Experience Manager upgrade documentation for your specific version path at helpx.adobe.com
  4. 4. Create a full backup of the AEM repository (crx-quickstart) and database before upgrading
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade to production environment, targeting version 6.5.24.0 or later (6.5.x branch) or version 2025.12.0 or later (newer release cadence)
  7. 7. Verify the upgrade was successful and the AEM instance is operational
  8. 8. Confirm the XSS vulnerability is remediated by testing the affected form fields
Caveat Major AEM upgrades may require content restructuring, custom code refactoring, or dependency updates; always test thoroughly in a staging environment 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-64593 — 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-64593 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