dbcve.org
DrupalCMS

CVE-2025-13081

MEDIUM · 5.9 CVSS v3.1 Published 2025-11-18
Fix available
A fix is available. Upgrade to 10.4.9 / 10.5.6 or later.
See remediation →
65/100
Remediation priority · Elevated
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.4.9, from 10.5.0 before 10.5.6, from 11.0.0 before 11.1.9, from 11.2.0 before 11.2.8.

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 an Object Injection vulnerability where improperly controlled modification of dynamically-determined object attributes allows attackers to inject malicious objects. This stems from insufficient validation of user-supplied input being used to set object properties, potentially enabling remote code execution or other attacks depending on available gadget chains in the Drupal environment.

MitigationUpgrade Drupal Core to version 10.4.9, 10.5.6, 11.1.9, or 11.2.8 or later. Before upgrading, audit custom modules and themes for compatibility and test thoroughly in a staging environment.

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.4.9>= 10.5.0, < 10.5.6>= 11.0.0, < 11.1.9>= 11.2.0, < 11.2.8

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/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 Drupal Core version
    Run 'drush core:status' or check the VERSION constant in core/lib/Drupal.php, or look at the 'system' table in the database for the 'drupal' entry
    Affected if The version falls within: 8.0.0 <= version < 10.4.9, OR 10.5.0 <= version < 10.5.6, OR 11.0.0 <= version < 11.1.9, OR 11.2.0 <= version < 11.2.8
  2. Verify PHP unserialization usage in custom code
    Search custom modules and themes for 'unserialize()' calls using grep -r "unserialize" --include="*.php" in the modules and themes directories
    Affected if Custom code uses unserialize() on user-supplied or untrusted data without prior validation
  3. Check for dangerous property manipulation patterns
    Search for code patterns that set object properties dynamically using user input, such as $$variable, $object->$property, or extract() on request data
    Affected if Code dynamically assigns properties to objects based on unvalidated user input
  4. Audit custom modules for potential gadget chains
    Review custom modules for classes with __wakeup, __destruct, __toString, or __call magic methods that could be chained for exploitation
    Affected if Custom modules contain exploitable magic methods that could be triggered via object injection

You are affected if your Drupal Core version is within the vulnerable ranges AND your environment contains exploitable patterns (untrusted unserialize calls or dynamic property assignment) that could trigger the object injection flaw.

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.4.9 / 10.5.6 / 11.1.9 or later
Fixed in 10.4.910.5.611.1.9
Interim mitigation

Upgrade Drupal Core to version 10.4.9, 10.5.6, 11.1.9, or 11.2.8 or later. Before upgrading, audit custom modules and themes for compatibility and test thoroughly in a staging environment.

Recommended fix High confidence

Drupal core 10.4.9+, 10.5.6+, 11.1.9+, or 11.2.8+ (depending on your current branch)

  1. 1. Backup the entire Drupal site including files and database
  2. 2. Determine the current Drupal version by running `drush status` or checking the CHANGELOG.txt file
  3. 3. For Drupal 10.4.x: upgrade to 10.4.9 or later; for 10.5.x: upgrade to 10.5.6 or later; for 11.0.x: upgrade to 11.1.9 or later; for 11.2.x: upgrade to 11.2.8 or later
  4. 4. Update Drupal core using Composer: `composer require drupal/core:^10.4.9 --no-interaction` (adjust version based on your current branch)
  5. 5. Run database updates: `drush updatedb` or `php core/scripts/drupal.php updatedb`
  6. 6. Clear all caches: `drush cr` or `drush cache-rebuild`
  7. 7. Verify the update was successful by checking the Drupal version and testing key functionality
Caveat Minor version upgrades typically have minimal breaking changes, but test in a staging environment first as with any core update

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

Fix this in Drupal Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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