dbcve.org
DrupalCMS

CVE-2025-3057

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 10.3.13 / 10.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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.13, from 10.4.0 before 10.4.3, from 11.0.0 before 11.0.12, from 11.1.0 before 11.1.3.

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

Drupal core contains a Cross-Site Scripting (XSS) vulnerability where improper input neutralization during web page generation allows attackers to inject malicious scripts into pages viewed by other users. This is a stored or reflected XSS affecting multiple Drupal core versions from 8.0.0 through 11.1.x.

MitigationUpgrade Drupal core to version 10.3.13, 10.4.3, 11.0.12, or 11.1.3 (or later) to patch the XSS vulnerability. Review and test custom modules for similar input sanitization issues.

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.13>= 10.4.0, < 10.4.3>= 11.0.0, < 11.0.12>= 11.1.0, < 11.1.3

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 Drupal core version
    Locate the VERSION constant in core/lib/Drupal.php, or run 'drush status' and look for 'Drupal version', or check the composer.json file in the docroot for the drupal/core version
    Affected if The installed version falls within any of these ranges: >= 8.0.0 and < 10.3.13; >= 10.4.0 and < 10.4.3; >= 11.0.0 and < 11.0.12; >= 11.1.0 and < 11.1.3
  2. Determine if the site accepts user input
    Review enabled modules and identify forms, comment systems, content creation fields, or any feature that allows users to submit text that gets stored and displayed to other users
    Affected if The site has any user-contributed content capability (comments, user profiles, nodes visible to others, rich text editors, or custom forms)
  3. Check for exposed input vectors in core or contrib modules
    Review the modules directory (modules/ and modules/contrib/) for any custom or third-party modules that handle user-submitted data and render it back without proper sanitization using Drupal's API functions like \Drupal\Component\Utility\Html::escape() or Twig's |escape filter
    Affected if Custom modules exist that render user input without using Drupal's sanitization functions, or if unvetted contributed modules are installed

You are affected if your Drupal core version is below 10.3.13, 10.4.3, 11.0.12, or 11.1.3 AND your site allows any user-submitted content to be displayed to other users.

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.13 / 10.4.3 / 11.0.12 or later
Fixed in 10.3.1310.4.311.0.12
Interim mitigation

Upgrade Drupal core to version 10.3.13, 10.4.3, 11.0.12, or 11.1.3 (or later) to patch the XSS vulnerability. Review and test custom modules for similar input sanitization issues.

Recommended fix High confidence

Upgrade to Drupal 10.3.13, 10.4.3, 11.0.12, or 11.1.3 (whichever corresponds to your current major version)

  1. 1. Backup your Drupal site database and files
  2. 2. Update Drupal core using Composer: `composer require drupal/core:^10.3.13 --no-interaction` (adjust version based on your current major release - use 10.4.3 for 10.4.x, 11.0.12 for 11.0.x, or 11.1.3 for 11.1.x)
  3. 3. Run database updates: `drush updatedb` or `php core/scripts/drupal update-db`
  4. 4. Clear all caches: `drush cr` or `php core/scripts/drupal cache-clear`
  5. 5. Verify the fix by navigating to /admin/reports/status and confirming the Drupal core version matches the target release
Caveat Minor version upgrades typically have no breaking changes; always review the release notes for any known issues before upgrading

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

Fix this in Drupal Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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