CVE-2024-55636
NoneCVSS
—
EPSS
0.9%
Published
Dec 10, 2024
CISA due date
—
Cloudanix analysis
A flaw in the Drupal content system could let attackers delete important files if they already have another way in, so updating to the newest version closes the gap.
- Exploitation
- Other
- Attacker needs
- Other
- Complexity
- High
- Impact
- Data Tampering
- Component
- Web Framework
- Class
- Deserialization
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Medium
What it actually does
The vulnerability allows PHP object injection through unsafe deserialization in Drupal core classes, which when chained with a separate input-passing flaw can result in arbitrary file deletion; type hints were added to affected class properties to prevent exploitation.
Why it matters to the business
Organizations running older Drupal versions face elevated risk of data loss or site compromise if an attacker chains this with another vulnerability, potentially disrupting operations and requiring emergency patching.
How an attack unfolds
An attacker first identifies and exploits a separate vulnerability that supplies attacker-controlled data to a Drupal unserialize call, then leverages the resulting object injection to delete arbitrary files on the server.
How to fix it
Upgrade Drupal core to 10.2.11 or later, 10.3.9 or later, or 11.0.8 or later; apply the commit 3712d59414f556474f990a503c3f7c295f8c719f; ensure any custom subclasses of affected core classes also declare property types.
How to confirm the fix worked
Verify Drupal version is at or above the fixed releases; review custom code extending core classes for missing type declarations; test that unserialize operations reject unsafe input.
Typical attack path
- Locate a secondary vulnerability allowing unsafe data to reach unserialize()
- Craft a serialized PHP object payload targeting vulnerable Drupal core classes
- Trigger deserialization to achieve arbitrary file deletion
- Use deleted files to disrupt service or enable further access
How to detect it
Review web server and application logs for unexpected file deletion events or errors related to unserialize operations; inspect for any evidence of chained exploits attempting to pass serialized data to Drupal endpoints.
What your security team should do
- Immediately upgrade all Drupal instances to the fixed versions listed
- Audit custom code for extensions of affected classes and add type hints
- Monitor for any chained deserialization attempts in application logs
- Prioritize patching given the potential for file deletion when combined with other flaws
The record
Drupal core contains a potential PHP Object Injection vulnerability that (if combined with another exploit) could lead to Artbitrary File Deletion. It is not directly exploitable. This issue is mitigated by the fact that in order to be exploitable, a separate vulnerability must be present that allows an attacker to pass unsafe input to `unserialize()`. There are no such known exploits in Drupal core. To help protect against this vulnerability, types have been added to properties in some of Drupal core's classes. If an application extends those classes, the same types may need to be specified on the subclass to avoid a `TypeError`. This issue affects Drupal Core: from 8.0.0 before 10.2.11, from 10.3.0 before 10.3.9, from 11.0.0 before 11.0.8.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Packagist | drupal/core | 10.3.0 | 10.3.9 |
| Packagist | drupal/core | 11.0.0 | 11.0.8 |
| Packagist | drupal/core | 8.0.0 | 10.2.11 |
| Packagist | drupal/core | 8.8.0 | 10.2.11 |
| Packagist | drupal/core-recommended | 10.3.0 | 10.3.9 |
| Packagist | drupal/core-recommended | 11.0.0 | 11.0.8 |
| Packagist | drupal/core-recommended | 8.8.0 | 10.2.11 |
| Packagist | drupal/drupal | 10.3.0 | 10.3.9 |
| Packagist | drupal/drupal | 11.0.0 | 11.0.8 |
| Packagist | drupal/drupal | 8.8.0 | 10.2.11 |
| Bitnami | drupal | 8.0.0 | 10.3.9 |
| Ubuntu:Pro:14.04:LTS | drupal7 | 0 | No fix |
| Ubuntu:Pro:16.04:LTS | drupal7 | 0 | No fix |
| packagist | drupal/core | 10.3.0 | 10.3.9 |
| packagist | drupal/core | 11.0.0 | 11.0.8 |
| packagist | drupal/core | 8.8.0 | 10.2.11 |
| packagist | drupal/core-recommended | 10.3.0 | 10.3.9 |
| packagist | drupal/core-recommended | 11.0.0 | 11.0.8 |
| packagist | drupal/core-recommended | 8.8.0 | 10.2.11 |
| packagist | drupal/drupal | 10.3.0 | 10.3.9 |
| packagist | drupal/drupal | 11.0.0 | 11.0.8 |
| packagist | drupal/drupal | 8.8.0 | 10.2.11 |
Related vulnerabilities
- GHSA-83v7-c2cf-p9c2 Drupal core allows Forceful Browsing Also affects drupal/core
- GHSA-h89p-5896-f4q8 Drupal core allows Content Spoofing Also affects drupal/core
- GHSA-mhpg-hpj5-73r2 Drupal core allows Exploiting Incorrectly Configured Access Control Security Levels Also affects drupal/core
- GHSA-m6vv-vcj8-w8m7 Drupal core allows Object Injection Also affects drupal/core
- CVE-2025-13081 Drupal core allows Object Injection Also affects drupal/core
- CVE-2025-13082 Drupal core allows Content Spoofing Also affects drupal/core
- CVE-2025-13083 Drupal core allows Exploiting Incorrectly Configured Access Control Security Levels Also affects drupal/core
- CVE-2025-13080 Drupal core allows Forceful Browsing Also affects drupal/core