dbcve.org
Experience ManagerApplication · Adobe

CVE-2025-46940

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 when other users view pages containing the compromised fields.

MitigationApply Adobe's security patch by upgrading to Adobe Experience Manager 6.5.23 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure 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. Identify installed AEM version
    Navigate to the AEM welcome page and check 'Version' under 'Platform Information', or run the command: curl -s http://localhost:4502/crx/packmgr/service.jsp?cmd=version | grep -i 'crx'
    Affected if Version is 6.5.22 or earlier, or version is before 2025.5.0 (and not 6.5.23.0 or later)
  2. Determine if Forms or custom form fields are in use
    Check the AEM Forms UI at /aem/forms.html or inspect the repository under /content/forms for custom form definitions, or query the CRX/DE Lite at /crx/de/index.jsp for nodes under /libs/fd or /apps/fd
    Affected if AEM Forms or custom form components are configured and accessible to low-privileged users
  3. Inspect form submission data for injected scripts
    Use CRX/DE Lite to browse form submission nodes under /content/forms/submissions, or check the Granite DataStore for any form field values containing script tags, script URLs, or javascript: handlers
    Affected if Form data contains unsanitized HTML/JavaScript in form field values that could execute when rendered
  4. Verify low-privileged user access to form authoring
    Log in as a user with minimal permissions (e.g., 'forms-user' group) and attempt to create or edit a form via the Adaptive Forms editor at /aem/forms.html/create/adaptive-form
    Affected if Low-privileged users can access and modify form fields without admin rights

You are affected if your AEM version is below 6.5.23.0 or below 2025.5.0 AND you have Forms or custom form fields exposed to low-privileged users who can inject malicious scripts that persist in the system.

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 Adobe's security patch by upgrading to Adobe Experience Manager 6.5.23 or later. Additionally, implement output encoding and input validation on form fields as a defense-in-depth measure until the patch is applied.

Recommended fix Moderate confidence

6.5.23.0 or later (6.5 branch); or 2025.5.0 or later (2025 branch)

  1. Identify the current Adobe Experience Manager version running in the environment
  2. Determine which release branch is in use (6.5.x or 2025.x)
  3. Plan an upgrade to the appropriate fixed version: 6.5.23.0 or later for the 6.5 branch, or 2025.5.0 or later for the newer branch
  4. Create a complete backup of the current AEM instance including repository, configuration, and custom code
  5. Test the upgrade in a non-production/staging environment to verify compatibility
  6. Execute the upgrade following Adobe's official AEM upgrade documentation
  7. Verify the upgrade was successful by checking the AEM version in the About Adobe Experience Manager page
  8. Confirm the XSS vulnerability is no longer present by reviewing the security patch notes for the new version
Caveat Minor version upgrades typically have minimal breaking changes; however, test custom components 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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