dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46964

MEDIUM · 5.4 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 6.5.23.0 / 2025.5.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.22 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.22 and earlier allows low-privileged users to inject malicious JavaScript into form fields. The injected payload persists in the system and executes in victim browsers when they view pages containing the compromised fields.

MitigationUpgrade Adobe Experience Manager to a version newer than 6.5.22, or apply the relevant security patch. Implement input validation and output encoding on form fields as a defense-in-depth measure.

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.23.0< 2025.5.0

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 AEM version
    Navigate to AEM Welcome page > Help > Version, or access /system/console/systeminfo, or check version.properties in crx-quickstart
    Affected if Version is below 6.5.23.0 or below 2025.5.0 (for cloud/2025 releases)
  2. Verify Forms or Adaptive Forms module is enabled
    Check if AEM Forms add-on is installed by navigating to /libs/granite/core/content/login.html or checking package manager for aem-forms-* packages
    Affected if AEM Forms or Adaptive Forms feature is installed and active
  3. Identify form-enabled content paths
    Search for Adaptive Form fragments or Form data model objects in crx/de lite under /content/forms or /content/dam/forms
    Affected if Form content exists in the repository under /content/forms or related paths
  4. Inspect user permission levels for forms
    Check user/group permissions in AEM Groups console or crx/explorer for users with 'content-author' or 'forms-user' assignments
    Affected if Low-privileged users (non-admin) have write access to form content or form fragments
  5. Audit existing form field content for malicious payloads
    Use crx/de lite to search jcr:content nodes under /content/forms for script tags, javascript:, or event handlers in text fields
    Affected if Any form field content contains unsanitized HTML/script tags or XSS attempt patterns

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND Forms/Adaptive Forms are enabled with low-privileged users having write access to form fields.

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.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Upgrade Adobe Experience Manager to a version newer than 6.5.22, or apply the relevant security patch. Implement input validation and output encoding on form fields as a defense-in-depth measure.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or 2025.5.0 (or later)

  1. Confirm current Adobe Experience Manager version by accessing the AEM welcome page or checking the version.properties file
  2. Download Adobe Experience Manager 6.5.23.0 (for 6.5.x branch) or 2025.5.0 (for cloud/continuous release) from the official Adobe Software Distribution portal
  3. Review the Adobe Experience Manager release notes for version 6.5.23.0 or 2025.5.0 for any specific migration or upgrade considerations
  4. Perform a full backup of the current AEM instance including the repository, database, and configuration files
  5. Test the upgrade in a non-production environment first to verify compatibility with custom code and integrations
  6. Execute the upgrade following Adobe's standard upgrade procedure for AEM 6.5 or the cloud release
  7. After upgrade, verify that the XSS vulnerability is resolved by testing the affected form fields
  8. Deploy to production once testing is complete
Caveat Review Adobe release notes for potential breaking changes between your current version and the target version before upgrading

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

Fix this in Experience Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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