dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46855

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

MitigationUpdate Adobe Experience Manager to version 6.5.23 or later; alternatively, implement proper input validation and output encoding on vulnerable form fields to prevent script injection.

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. Confirm Adobe Experience Manager is installed
    Look for AEM installation directories (commonly in /opt/aem, /apps/aem, or C:\Program Files\Adobe) or check for AEM processes running on common ports (4502, 4503)
    Affected if AEM is not present in the environment, the vulnerability does not apply
  2. Determine the installed AEM version
    Access the AEM Web Console (System > Information) at /system/console/configMgr or check the version.properties file in the AEM installation directory
    Affected if Cannot determine version - verification cannot proceed
  3. Compare installed version to affected ranges
    Check if the version is below 6.5.23.0 or below 2025.5.0. For 6.x versions, look at the 6.5.x line; for Cloud/2025 versions, look at the 2025.x line
    Affected if Version is 6.5.22.x or earlier, or 2025.0.x through 2025.4.x - the environment is within affected version ranges
  4. Verify Forms or Adaptive Forms feature is enabled
    Check if AEM Forms or Adaptive Forms components are installed by reviewing the package manager (/crx/packmgr) for af-core or forms packages, or check the AEM console for Forms functionality
    Affected if Forms/Adaptive Forms are not installed or not in use, the specific attack surface may not be present
  5. Confirm low-privileged user access exists
    Review user permissions in AEM User Management (/security/users.html or /libs/granite/security/content/useradmin) to see if non-admin users have access to create or edit form content
    Affected if Only admin users exist or low-privileged users cannot access form authoring, exploitation is not possible in practice

You are affected if Adobe Experience Manager is running with a version below 6.5.23.0 or below 2025.5.0 and Forms functionality with low-privileged user access is enabled in the environment.

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 version 6.5.23 or later; alternatively, implement proper input validation and output encoding on vulnerable form fields to prevent script injection.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or 2025.5.0 (or later)

  1. 1. Back up your current Adobe Experience Manager instance, including the repository and database
  2. 2. Download Adobe Experience Manager version 6.5.23.0 or 2025.5.0 (or later) from the official Adobe distribution portal or Software Distribution
  3. 3. Follow Adobe's official upgrade documentation for your specific deployment type (tarmk or mongodb-based)
  4. 4. Run the upgrade using the author instance first, then replicate configuration to publish instances
  5. 5. After upgrade, clear browser cache and verify the fix by testing form fields for XSS payload injection
  6. 6. Validate that all custom code and integrations function correctly post-upgrade
Caveat No major breaking changes noted in provided materials; standard regression testing recommended for custom components

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 / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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