dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46859

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

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure until the patch can be applied.

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. Determine AEM version
    Access the AEM Welcome page or use the Version manifest at /system/console/bundles or check the crx-quickstart/packageMgr.xml file for the installed version string
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0
  2. Identify form field components
    Review the AEM Forms or Adaptive Forms implementation in the /libs or /apps directories. Check form field components for presence of input validation or output encoding settings
    Affected if Form fields lack proper output encoding or input validation on user-controllable fields
  3. Audit user group permissions
    Use the AEM User Admin console at /security/useradmin to examine group permissions for low-privileged users. Verify if standard users can access and submit forms that persist data
    Affected if Low-privileged users have create or modify permissions on form content nodes in the repository
  4. Scan for existing XSS payloads
    Query the repository for stored script tags using CRXDE Lite search or a repository export. Look for <script> tags, javascript: URLs, or event handlers in form submission data nodes under /content or /var
    Affected if Malicious script content is found persisted in form data nodes

You are affected if your AEM version is below 6.5.23.0 (or below 2025.5.0) AND your forms accept user input that is stored without output encoding, allowing a low-privileged attacker to inject persistent 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.23.0 / 2025.5.0 or later
Fixed in 6.5.23.02025.5.0
Interim mitigation

Update Adobe Experience Manager to a version newer than 6.5.22. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure until the patch can be applied.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 (for 6.5.x on-premises) or 2025.5.0 (for Cloud Service)

  1. 1. Identify the current Adobe Experience Manager version in use (check /system/console/info or CRXDE Lite version properties)
  2. 2. Determine which release line applies to your instance: 6.5.x (on-premises) or Cloud Service (2025.x release train)
  3. 3. For AEM 6.5.x on-premises: Plan upgrade to version 6.5.23.0
  4. 4. For AEM as a Cloud Service: Plan upgrade to version 2025.5.0 or later
  5. 5. Create a full backup of the current AEM instance including repository, database, and configurations
  6. 6. Test the upgrade in a non-production environment first
  7. 7. Review Adobe's release notes for 6.5.23.0 or 2025.5.0 for any migration requirements or configuration changes
  8. 8. Execute the upgrade following Adobe's standard upgrade documentation
Caveat Review release notes for potential breaking changes; major version upgrades may require content repository migrations or configuration adjustments

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-46859 — 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-46859 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