dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46966

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

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability that allows low-privileged attackers to inject malicious JavaScript into form fields. The injected payload persists in the system and executes in victim users' browsers when they navigate to pages containing the compromised form fields.

MitigationApply the vendor-provided patch (AEM 6.5.23 or later) to address the vulnerability. Additionally, implement input validation and output encoding on form fields as defense-in-depth measures.

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
    Access the AEM Web Console (typically at /system/console/configMgr) or check the version file in the installation directory. Compare the version number to the affected ranges: versions before 6.5.23.0 or before 2025.5.0.
    Affected if The installed version is less than 6.5.23.0 or less than 2025.5.0.
  2. Identify AEM Forms module presence
    Check if AEM Forms is installed by navigating to the Forms section in AEM (typically at /aem/forms) or by reviewing installed packages in the Package Manager.
    Affected if AEM Forms or form-related packages are installed and active.
  3. Verify low-privilege user access to forms
    Review user group permissions in AEM User Management (accessible at /libs/granite/security/content/useradmin) and check if users with Contributor or lower privileges have access to create or edit form content.
    Affected if Low-privilege users (Contributor level or below) have permissions to create, edit, or submit form fields.
  4. Inspect stored form field content for malicious scripts
    Use CRX/DE (accessible at /crx/de) to query form field content nodes under /content or /apps where forms store submitted data. Look for script tags, javascript: URIs, or event handlers in field values.
    Affected if Form field content nodes contain unsanitized HTML, script tags, or JavaScript event handlers.

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND AEM Forms is enabled AND low-privilege users can access form editing, or if malicious script payloads are already present in form field content.

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

Apply the vendor-provided patch (AEM 6.5.23 or later) to address the vulnerability. Additionally, implement input validation and output encoding on form fields as defense-in-depth measures.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (or later) / 2025.5.0 (or later for Cloud Service)

  1. Verify current Adobe Experience Manager version by navigating to /system/console/bundles or checking the AEM welcome page
  2. Review the AEM upgrade documentation for your current version at https://helpx.adobe.com/experience-manager/6-5.html
  3. Plan and schedule a maintenance window for the upgrade process
  4. Back up the current AEM instance including repository, database, and configuration files
  5. Stop the AEM instance before beginning the upgrade
  6. Upgrade to Adobe Experience Manager 6.5.23.0 or later (or 2025.5.0 or later for Cloud Service)
  7. Start the upgraded AEM instance and verify all bundles are active
  8. Test critical workflows and forms to ensure functionality is intact
Caveat Review Adobe's 6.5.23 release notes for any deprecation notices or breaking changes that may affect custom components or integrations

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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