dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46899

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 on the page and executes in victims' browsers when they view the affected content.

MitigationUpdate Adobe Experience Manager to a version newer than 6.5.22, or implement input validation and output encoding on affected form fields to neutralize malicious 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. Check Adobe Experience Manager version
    Navigate to the AEM Welcome page or access the system information via the Help menu, or query the version via the OSGi console at /system/console/bundles, or check the crx-quickstart/package.version file
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0
  2. Verify if Forms or Adaptive Forms module is enabled
    Access the AEM Forms console at /aem/forms or check the OSGi component list for forms-related packages under /system/console/components
    Affected if Forms or Adaptive Forms are installed and enabled, creating vulnerable form field entry points
  3. Identify accessible form field components
    Review the AEM Forms templates and adaptive form configurations under /conf or /libs/forms, or check the Form Models in the AEM Assets console
    Affected if Form components with user input fields are published and accessible to low-privileged authors or public users
  4. Check for low-privilege user authoring permissions
    Review user/group permissions in AEM User Management at /security/users.html or /security/groups.html, specifically looking for contributors or content-authors with form creation rights
    Affected if Low-privilege users (contributors, content-authors) have permission to create or edit form content that gets published

If the AEM version is below 6.5.23.0 (or below 2025.5.0) and Forms with user input fields are accessible to low-privilege authors, the environment is vulnerable to stored XSS via form injection.

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, or implement input validation and output encoding on affected form fields to neutralize malicious script injection.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or 2025.5.0

  1. Verify current Adobe Experience Manager version by accessing the AEM welcome page or checking the version properties
  2. Back up the current AEM instance including the repository, database, and configuration files
  3. Download Adobe Experience Manager 6.5.23.0 (for 6.x users) or 2025.5.0 (for cloud/2024.x users) from Adobe's official distribution portal
  4. Stop the AEM instance before applying the upgrade
  5. Install the upgrade following Adobe's standard upgrade documentation for your specific deployment type (standalone, cluster, etc.)
  6. After installation, verify the upgrade was successful by checking the AEM version number
  7. Test critical workflows and form submissions to ensure the XSS fix does not impact legitimate functionality
  8. Validate that the fix resolves the vulnerability by attempting to submit test XSS payloads in vulnerable form fields
Caveat Review Adobe's release notes for the target version to identify any breaking changes specific to your deployment configuration

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