dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46936

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

Adobe Experience Manager versions 6.5.22 and earlier contain a stored Cross-Site Scripting (XSS) vulnerability in form fields. A low-privilege authenticated attacker can inject malicious JavaScript into vulnerable form inputs, which persists on the page and executes in the browsers of users who view the affected content.

MitigationUpgrade Adobe Experience Manager to version 6.5.23 or later. As a temporary measure, implement strict input validation and output encoding on all form fields, and restrict low-privilege user permissions until the patch is applied.

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 AEM version
    Access the AEM Welcome page or check the product version through the system console (Help > About Adobe Experience Manager). Compare the displayed version against the affected ranges: below 6.5.23.0 or below 2025.5.0.
    Affected if The installed version is 6.5.22 or earlier, or falls below 6.5.23.0 or 2025.5.0.
  2. Identify low-privilege user accounts
    Review user permissions in the AEM User Management console (Tools > Security > Users or Tools > Security > Groups). Determine if users with limited or contributor-level permissions have the ability to create or edit content containing form fields.
    Affected if Low-privilege authenticated users exist and have write access to form-enabled content.
  3. Locate form field components
    Review the AEM instance for components that accept user-generated input in forms, such as text fields, textarea, or custom form containers. Check if these components are exposed in any accessible content pages or templates.
    Affected if Form input components are present and accessible to low-privilege users for content creation.
  4. Verify content creation access
    Test whether a low-privilege user can create or edit pages containing form fields. Log in with a test low-privilege account and attempt to add content with form components to confirm the attack surface exists.
    Affected if Low-privilege users can create or edit content with form input fields on published pages.

Your environment is affected if AEM version is below 6.5.23.0 or below 2025.5.0 AND low-privilege authenticated users can access and inject content into form fields that are rendered on accessible pages.

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

Upgrade Adobe Experience Manager to version 6.5.23 or later. As a temporary measure, implement strict input validation and output encoding on all form fields, and restrict low-privilege user permissions until the patch is applied.

Recommended fix High confidence

Adobe Experience Manager 6.5.23.0 or later (6.5.x line); Adobe Experience Manager 2025.5.0 or later (cloud/2025 line)

  1. Back up the current Adobe Experience Manager instance and all content repositories
  2. Download Adobe Experience Manager 6.5.23.0 (for 6.5.x customers) or 2025.5.0 (for cloud customers) from the official Adobe distribution portal
  3. Install the updated AEM version following Adobe's standard upgrade documentation
  4. After upgrade, verify the version number reflects the patched release (6.5.23.0 or 2025.5.0)
  5. Test that form functionality works correctly and the XSS vulnerability is no longer exploitable
Caveat Standard AEM upgrade risks apply - test thoroughly in non-production environment before deploying to production

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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