dbcve.org
DrupalCMS

CVE-2025-31675

MEDIUM · 5.4 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 10.3.14 / 10.4.5 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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Drupal core allows Cross-Site Scripting (XSS).This issue affects Drupal core: from 8.0.0 before 10.3.14, from 10.4.0 before 10.4.5, from 11.0.0 before 11.0.13, from 11.1.0 before 11.1.5. It also affects the Drupal 7 module from versions 7.x-1.0 through 7.x-1.12.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Drupal core where user-supplied input is not properly sanitized before being rendered in web pages. An authenticated attacker could inject malicious JavaScript that executes in the browsers of other users viewing the affected content.

MitigationUpdate Drupal core to version 10.3.14, 10.4.5, 11.0.13, or 11.1.5 (depending on the active branch), or update the Drupal 7 module to version 7.x-1.13 or later to remediate this vulnerability.

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
DrupalCMS
Affected:>= 8.0.0, < 10.3.14>= 10.4.0, < 10.4.5>= 11.0.0, < 11.0.13>= 11.1.0, < 11.1.5

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 installed Drupal core version
    Run `drush status` or inspect the `core/lib/Drupal.php` file for the VERSION constant, or check the `composer.json` file for the `drupal/core` version constraint
    Affected if The installed version is >= 8.0.0 and < 10.3.14, OR >= 10.4.0 and < 10.4.5, OR >= 11.0.0 and < 11.0.13, OR >= 11.1.0 and < 11.1.5
  2. Verify user authentication is enabled
    Confirm that the Drupal site has user registration or admin-created user accounts enabled. Check the People configuration page or inspect the user_role table in the database
    Affected if Authenticated user accounts can be created or exist on the site (this is enabled by default in Drupal installations)
  3. Identify user input submission points
    Review which content types, webforms, or comment forms accept user-supplied input. Check the node_type table and field_config tables for enabled text fields
    Affected if The site contains any content type, comment, or form that accepts and stores user input, which is typical in Drupal installations

If the Drupal core version falls within any of the affected ranges AND the site allows authenticated users to submit content, the environment is vulnerable to stored XSS via CVE-2025-31675.

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 10.3.14 / 10.4.5 / 11.0.13 or later
Fixed in 10.3.1410.4.511.0.13
Interim mitigation

Update Drupal core to version 10.3.14, 10.4.5, 11.0.13, or 11.1.5 (depending on the active branch), or update the Drupal 7 module to version 7.x-1.13 or later to remediate this vulnerability.

Recommended fix High confidence

Upgrade to Drupal 10.3.14, 10.4.5, 11.0.13, or 11.1.5 (whichever is the next minor release for your current branch)

  1. 1. Identify your current Drupal core version by checking the core/lib/Drupal.php file or running `drush status`
  2. 2. Determine which upgrade path applies to your current version from: 8.0.0-10.3.x -> upgrade to 10.3.14+, 10.4.x -> upgrade to 10.4.5+, 11.0.x -> upgrade to 11.0.13+, or 11.1.x -> upgrade to 11.1.5+
  3. 3. Create a complete backup of your database and files before upgrading
  4. 4. Put your site in maintenance mode via Admin > Configuration > Development > Maintenance mode or `drush site-install`
  5. 5. Update Drupal core using your preferred method: Composer (`composer require drupal/core:^10.3.14 --update-with-dependencies`), Drush (`drush up drupal`), or manual file replacement
  6. 6. Run database updates: `drush updatedb` or visit /update.php
  7. 7. Clear all caches: `drush cr` or Admin > Configuration > Development > Performance > Clear all caches
  8. 8. Verify the upgrade was successful and test critical functionality
Caveat Drupal minor version upgrades typically have minimal breaking changes; review the release notes for your target version for any deprecation notices or configuration changes

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

Fix this in Drupal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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