dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46954

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

MitigationApply the appropriate AEM patch or update to a version beyond 6.5.22, and implement output encoding/sanitization for all user-supplied data in form fields.

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 System Information console at /system/console/systeminfo or check the crx-quickstart/package.properties file for the productVersion field
    Affected if The version listed is below 6.5.23.0 or below 2025.5.0 (if running a 2025 release)
  2. Verify AEM release track
    Identify whether the installation is on the 6.5.x LTS release line or the 2025 quarterly release line by reviewing the version string format
    Affected if The installation is on the 6.5.x track at version 6.5.22 or lower, or on the 2025 track below 2025.5.0
  3. Identify custom form components in use
    Review the AEM Forms or custom form components deployed in the system by accessing the CRX/DE Lite console at /crx/de and examining /apps for custom form field components
    Affected if Custom form components that accept user input are present in the /apps directory without proper output encoding
  4. Audit form field data for existing scripts
    Query the repository using CRX/DE Lite or the Query Builder API to search for stored scripts in form field content nodes, looking for patterns like script tags or javascript: in stored values
    Affected if Any form field content nodes contain unsanitized script tags or JavaScript event handlers
  5. Check low-privileged user permissions on forms
    Review group permissions in AEM User Admin at /useradmin to determine if low-privilege users (contributors, content authors) have access to create or edit form components
    Affected if Users with limited permissions can access form creation or editing interfaces

You are affected if your AEM version is below 6.5.23.0 (for 6.5.x releases) or below 2025.5.0 (for 2025 releases) AND your system uses custom form fields that accept user input without server-side output encoding.

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 appropriate AEM patch or update to a version beyond 6.5.22, and implement output encoding/sanitization for all user-supplied data in form fields.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (for 6.5.x line) or 2025.5.0 (for AEM as a Cloud Service)

  1. Confirm current Adobe Experience Manager version by accessing /system/console/configMgr or checking the AEM welcome page
  2. Review the Adobe Experience Manager 6.5.23.0 or 2025.5.0 release notes on helpx.adobe.com for upgrade requirements and changes
  3. Schedule a maintenance window and perform a full backup of the AEM instance, including the repository and database
  4. For AEM 6.5.x: Upgrade to version 6.5.23.0 or later by applying the latest Service Pack
  5. For AEM as a Cloud Service: Ensure the environment is updated to version 2025.5.0 or later through Cloud Manager
  6. Test the upgrade in a staging environment before deploying to production
  7. After upgrade, verify that the vulnerable form fields no longer accept malicious script payloads
Caveat Point releases typically contain backward-compatible fixes; however, always review release notes for any behavior 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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