dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46900

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 attacker can inject malicious JavaScript payloads into vulnerable form inputs, which persist in the system. When legitimate users browse to pages containing these compromised form fields, the malicious script executes in their browsers, potentially allowing session hijacking, credential theft, or defacement.

MitigationApply the vendor patch for AEM 6.5.22 or later. Additionally, implement output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.

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 AEM version
    Access the AEM Web Console (Help > System Information or /system/console/status.html) to view the current product version. Alternatively, check the manifest file in the AEM quickstart jar or the version.properties file in the crx-quickstart folder.
    Affected if The installed version is below 6.5.23.0 or below 2025.5.0 (for cloud/flex versions)
  2. Locate form field components
    Review the AEM Forms implementation by accessing the Forms & Documents console (/aem/forms.html) or examining the /content/forms/af node in the CRX/DE repository. Identify which adaptive forms or core components are in use.
    Affected if Adaptive Forms or Form Core Components are deployed and users can submit form data
  3. Inspect form data repositories for XSS payloads
    Query the JCR repository (via CRXDE Lite at /crx/de or using the Query Manager) for stored form submissions containing suspicious patterns. Search nodes under /content/forms/af for patterns like <script>, javascript:, onerror=, onload=, or other HTML/script tags in form field values.
    Affected if Any form submissions contain unsanitized HTML or script tags stored in form field data nodes
  4. Review recent form submissions for malicious content
    Check the Form Data Model service or the persistence layer for recent form submissions. Use AEM Forms dashboard or query the submission nodes at /content/forms/fp or custom submission endpoints for unusual script content.
    Affected if Recent form submissions contain JavaScript code or HTML markup in text input fields

A user is affected if their AEM version is below 6.5.23.0 (or 2025.5.0 for newer releases) AND they have forms with fields that accept user input and store data in the repository.

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 for AEM 6.5.22 or later. Additionally, implement output encoding on form fields and consider Content Security Policy headers to mitigate XSS execution.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or Adobe Experience Manager 2025.5.0

  1. Backup the current Adobe Experience Manager instance including repository, database, and configurations
  2. Download Adobe Experience Manager version 6.5.23.0 (for 6.x customers) or 2025.5.0 (for Cloud Service customers) from official Adobe channels
  3. Test the upgrade thoroughly in a non-production/staging environment before deploying to production
  4. Deploy the fixed version to production following standard AEM upgrade procedures
  5. Verify the patch is applied by checking the AEM version in the About Adobe Experience Manager information
Caveat Standard AEM upgrade precautions apply - test custom code and integrations in staging 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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,870
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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