dbcve.org
DrupalCMS

CVE-2025-31674

HIGH · 7.5 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 →
81/100
Remediation priority · High
Remotely reachable Zero-click

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
Improperly Controlled Modification of Dynamically-Determined Object Attributes vulnerability in Drupal Drupal core allows Object Injection.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

Object injection vulnerability in Drupal core allows remote attackers to manipulate dynamically-determined object attributes through improper validation, potentially leading to code execution or other malicious actions.

MitigationUpgrade Drupal core to version 10.3.13, 10.4.3, 11.0.12, or 11.1.3 or later to patch the object injection 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.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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Locate Drupal core version file
    Check the composer.json file in your Drupal root directory for the 'drupal/core' version entry, or view the CHANGELOG.txt file which displays the version number at the top
    Affected if The version shown is 8.0.0 or higher but below 10.3.13, OR 10.4.0 to below 10.4.3, OR 11.0.0 to below 11.0.12, OR 11.1.0 to below 11.1.3
  2. Verify version via Drush
    Run `drush status` or `drush core:status` from your Drupal web root to display the installed Drupal version
    Affected if The reported Drupal version falls within any of the affected ranges listed above
  3. Check Drupal.php constant
    Inspect the file core/lib/Drupal.php for the VERSION constant, which contains the exact Drupal core version number
    Affected if The VERSION constant value matches an affected version range from 8.0.0 through 11.1.2
  4. Confirm database-driven version
    Query the database: SELECT value FROM config WHERE name = 'system.site' and inspect the 'version' field in the JSON data
    Affected if The stored version matches any of the vulnerable version ranges

You are affected if your installed Drupal core version falls within any of these ranges: 8.0.0 to 10.3.12, 10.4.0 to 10.4.2, 11.0.0 to 11.0.11, or 11.1.0 to 11.1.2

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 object injection vulnerability.

Recommended fix High confidence

Upgrade to the latest patch version in your current branch: 10.3.13, 10.4.3, 11.0.12, or 11.1.3 (or later releases)

  1. 1. Back up your Drupal site database and files before proceeding with any upgrade.
  2. 2. Identify your current Drupal version by checking the CHANGELOG.txt file or running `drush status`.
  3. 3. For Drupal 10.3.x: Upgrade to version 10.3.13 or later.
  4. 4. For Drupal 10.4.x: Upgrade to version 10.4.3 or later.
  5. 5. For Drupal 11.0.x: Upgrade to version 11.0.12 or later.
  6. 6. For Drupal 11.1.x: Upgrade to version 11.1.3 or later.
  7. 7. If upgrading across major versions (e.g., from 9.x to 10.x or 10.x to 11.x), review the upgrade instructions at https://www.drupal.org/docs/upgrading-drupal.
  8. 8. Run `drush updatedb` or access /update.php to run database updates after core upgrade.
Caveat Cross-branch upgrades (e.g., 9.x to 10.x, 10.x to 11.x) may require module compatibility review and can have breaking changes; minor/patch upgrades within the same branch typically have minimal breaking changes

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

Fix this in Drupal Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
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,992.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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