dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46932

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-20
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

A stored Cross-Site Scripting (XSS) vulnerability in Adobe Experience Manager versions 6.5.22 and earlier allows low-privileged attackers to inject malicious JavaScript into form fields. The payload persists in the system and executes in victims' browsers when they navigate to pages containing the compromised fields.

MitigationApply input validation and output encoding to all form fields in AEM, and implement Content Security Policy (CSP) 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 the installed AEM version
    Access the AEM About page (Help > About Adobe Experience Manager) or query the version via the OSGi console at /system/console/status/productinfo. Look for the exact version number displayed.
    Affected if The version is below 6.5.23.0 or below 2025.5.0, placing the instance in the affected range.
  2. Confirm Forms or Adaptive Forms are in use
    Check if AEM Forms or Adaptive Forms components are installed and active. Navigate to the Forms section in AEM Assets or check for form-related packages in the Package Manager. Look for content structures under /content/forms or similar form-enabled directories.
    Affected if AEM Forms or Adaptive Forms are enabled and form definitions exist in the repository.
  3. Inspect form field data for suspicious content
    Use CRXDE Lite (accessible at /crx/de) or query the repository via the AEM Query Builder. Search under form content paths (such as /content/forms) for stored field values containing script tags, javascript: URIs, or event handler attributes like onload, onerror, or onmouseover.
    Affected if Form field values contain encoded or raw script tags, JavaScript URIs, or event handler attributes that were not intentionally authored.
  4. Review recent form submissions for injected payloads
    If AEM Forms data storage is in use, access the Forms Manager or query the data store for recent form submissions. Look for unexpected patterns in submitted field values that resemble XSS payloads.
    Affected if Form submission data contains unexpected script content or HTML markup in text fields.

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 and you have Forms or Adaptive Forms enabled with stored form data that may contain injected 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

Apply input validation and output encoding to all form fields in AEM, and implement Content Security Policy (CSP) headers to mitigate XSS execution.

Recommended fix High confidence

AEM 6.5.23.0 or later, or AEM 2025.5.0 or later

  1. Back up the current AEM instance and all content repositories before proceeding with the upgrade
  2. Review the official Adobe Experience Manager upgrade documentation for version 6.5.23.0 or 2025.5.0 release
  3. Test the upgrade in a non-production environment first to ensure compatibility with custom code and configurations
  4. Upgrade the AEM instance to version 6.5.23.0 or later (for 6.x releases), or to version 2025.5.0 or later (for the 2025 release cycle)
  5. After upgrade, verify that the stored XSS vulnerability in form fields has been remediated by testing with appropriate XSS payloads
  6. Deploy the upgraded instance to production after successful validation
Caveat Review Adobe's release notes for 6.5.23.0/2025.5.0 for potential breaking changes and custom code compatibility before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Experience Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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