DrupalCMS
CVE-2024-55636
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 · uneditedDeserialization of Untrusted Data vulnerability in Drupal Core allows Object Injection.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. Drupal core contains a chain of methods that is exploitable when an insecure deserialization vulnerability exists on the site. This so called gadget chain presents no direct threat, but is a vector that can be used to achieve remote code execution if the application deserializes untrusted data due to another vulnerability.
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 confidenceThis is a PHP object injection gadget chain in Drupal Core. The vulnerability exists as a chain of methods that becomes dangerous when paired with another insecure deserialization vulnerability on the site, potentially allowing remote code execution. It is not directly exploitable on its own but amplifies the severity of any existing deserialization flaw.
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
>= 8.0.0, < 10.2.11>= 10.3.0, < 10.3.9>= 11.0.0, < 11.0.8CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Drupal Core versionLocate the VERSION file in the Drupal root (core/lib/Drupal.php or composer.json) or run 'drush status' to retrieve the installed Drupal version. Alternatively, check the VERSION constant in the Drupal\Core\Drupal class.Affected if The installed version falls within these ranges: >= 8.0.0 and < 10.2.11, OR >= 10.3.0 and < 10.3.9, OR >= 11.0.0 and < 11.0.8.
-
Identify unsafe unserialize() calls in custom codeSearch the codebase for uses of unserialize() without a defined allowed_classes array. Search in modules/custom, themes/custom, and any custom profiles. Use grep or similar: grep -r 'unserialize(' --include='*.php' in the docroot, then inspect each call to determine if it handles untrusted user input.Affected if Any unserialize() call that processes untrusted input without specifying allowed_classes is present and could potentially chain with the gadget chain.
-
Inspect PHP unserialize configuration in settings.phpExamine sites/default/settings.php (or the appropriate settings.php for your site) for any unserialize_options configuration that permits untrusted deserialization, or check if the $settings['php_unserialize_options'] array is configured with allowed_classes set to false or not properly restricted.Affected if The PHP unserialize options are configured to allow unsafe deserialization of arbitrary classes.
-
Audit contributed modules for deserialization issuesReview all contributed modules (in modules/contrib) for any known deserialization vulnerabilities or unsafe unserialize() usage. Check Drupal's security advisories for installed modules and verify each module is up to date.Affected if Any installed module contains a deserialization vulnerability that could be chained with the Drupal Core gadget chain.
You are affected if your Drupal Core version is within the vulnerable ranges AND your site has any insecure deserialization mechanism (unsafe unserialize() calls or related vulnerabilities) that could invoke the gadget chain methods.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.2.1110.3.911.0.8
Update Drupal Core to version 10.2.11, 10.3.9, or 11.0.8. Additionally, audit custom code and contributed modules for unsafe unserialize() calls or other deserialization vulnerabilities that could chain with this gadget.
Drupal 10.2.11, 10.3.9, or 11.0.8 (depending on current major version branch)
- Backup the entire Drupal site including database and all files
- Verify current Drupal Core version using 'drush status' or admin/reports/status
- Determine which upgrade path applies based on current version (10.2.x, 10.3.x, or 11.0.x)
- Run 'composer require drupal/core:^10.2.11 --no-interaction' or appropriate version for your branch
- Run 'composer update drupal/core --with-all-dependencies' to update dependencies
- Clear composer cache if needed and retry the update
- Run database updates using 'drush updb' or visit update.php
- Clear all Drupal caches using 'drush cr'
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 / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-55636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-55636 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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