dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46904

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 authenticated attacker can inject malicious JavaScript into form input fields, which persists in the system. When other users subsequently browse to pages containing these compromised form fields, the embedded malicious script executes in their browsers, enabling session hijacking, credential theft, or defacement.

MitigationApply the vendor patch or update Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on all 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. Identify installed Adobe Experience Manager version
    Access the AEM Welcome page and locate the version information, or query the version endpoint at /system/console/config/org.apache.sling.jcr.base.internal.LoginAdminWhitelist~default.cfg.json to retrieve version details
    Affected if The displayed version number is below 6.5.23.0 (for 6.x releases) or below 2025.5.0 (for Cloud releases)
  2. Verify AEM 6.5.x release version
    Check the version.properties file in the crx-quickstart directory or access the CRX Package Manager at /crx/packmgr/list.jsp to confirm the exact AEM 6.5.x release version
    Affected if The installed 6.5.x version is 6.5.22 or earlier
  3. Verify AEM as a Cloud Service version
    Check the Cloud Manager environment details or access the Developer Console to view the AEM as a Cloud Service release version
    Affected if The installed cloud version is earlier than the 2025.5.0 release
  4. Confirm presence of form components
    Review the AEM implementation for usage of Adaptive Forms, Core Components form fields (core/wcm/components/form/*), or custom form implementations that store user input
    Affected if Form components that persist user input are present and the AEM version is in the affected range

Your environment is affected if the installed Adobe Experience Manager version is 6.5.22 or earlier for the 6.x line, or earlier than 2025.5.0 for the Cloud Service line, and you have form components that accept and store user input.

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 patch or update Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on all form fields as a defense-in-depth measure.

Recommended fix High confidence

6.5.23.0 (for 6.5.x branch) or 2025.5.0 (for cloud/year-based releases)

  1. Review Adobe Experience Manager release notes for versions 6.5.23.0 and 2025.5.0 to understand the security fix and any noted changes
  2. Backup your current AEM instance before proceeding with any upgrade
  3. Plan the upgrade, including testing any custom components, workflows, or integrations that may be affected
  4. Upgrade your AEM 6.5.x installation to version 6.5.23.0 or later, OR upgrade to 2025.5.0 if using the cloud release track
  5. After upgrade, verify that the stored XSS vulnerability in form fields has been remediated by reviewing the security patch details
  6. Deploy the upgraded version to production after successful validation in non-production environments
Caveat Standard upgrade considerations apply - test custom code, integrations, and workflows 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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