dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46890

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 where low-privileged attackers can inject malicious JavaScript into form fields. The malicious payload persists in the system and executes in victim users' browsers when they view pages containing the compromised fields.

MitigationUpdate Adobe Experience Manager to version 6.5.23 or later to receive the vendor patch. Until patched, restrict low-privileged user access to form creation/editing and consider implementing Content Security Policy headers 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. Determine installed AEM version
    Access the AEM Welcome page and navigate to Help > About Adobe Experience Manager, or query the version via the system console at /system/console/systeminfo. Look for the full version number in the Product Version field.
    Affected if The version is 6.5.22 or earlier, or falls below 2025.5.0.
  2. Verify Forms add-on is enabled
    Navigate to Package Manager (/crx/packmgr) and check if the 'aem-forms' or 'forms' package is installed. Alternatively, check /libs/fox/forms for the presence of form-related content structures.
    Affected if Forms functionality is present and accessible in the environment.
  3. Check low-privileged user access to form authoring
    Navigate to Tools > Security > Permissions or /useradmin and review groups assigned to low-privileged users (such as 'content-authors'). Check if these groups have create or modify permissions on /content/forms or /libs/forms paths.
    Affected if Low-privileged users have write permissions to form fields or form definitions.
  4. Inspect stored form data for malicious payloads
    Query the repository using CRXDE Lite (/crx/de) or the Query debugger. Search JCR content under /content/forms and /content/dam/forms for suspicious script tags, event handlers (onerror, onload, onclick), or javascript: protocols in text fields.
    Affected if Form field content contains unsanitized 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 Forms are enabled with low-privileged users having form authoring access.

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 to receive the vendor patch. Until patched, restrict low-privileged user access to form creation/editing and consider implementing Content Security Policy headers as a defense-in-depth measure.

Recommended fix High confidence

6.5.23.0 or 2025.5.0 (depending on current major version)

  1. 1. Identify the current Adobe Experience Manager version in use (check /system/console/bundles or About Adobe Experience Manager page)
  2. 2. If running 6.5.x version: Plan upgrade to 6.5.23.0 or later
  3. 3. If running 2024.x version: Plan upgrade to 2025.5.0 or later
  4. 4. Review Adobe Experience Manager release notes for the target version for any breaking changes
  5. 5. Create a backup of the current AEM instance and content repository
  6. 6. Schedule a maintenance window for the upgrade
  7. 7. Perform the upgrade following Adobe's official upgrade documentation
  8. 8. After upgrade, verify the XSS fix is applied by testing form field inputs with malicious script payloads
Caveat Review Adobe Experience Manager 6.5.23.0 and 2025.5.0 release notes for potential breaking changes and deprecations before upgrading

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