DrupalCMS
CVE-2026-55808
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 · uneditedImproper 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 versions: from 0.0.0 to 10.5.12, from 10.6.0 to 10.6.11, from 11.2.0 to 11.2.14, from 11.3.0 to 11.3.12, from 0.0.0 to 11.0.*, from 0.0.0 to 11.1.*.
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 · moderate confidenceCross-Site Scripting (XSS) vulnerability in Drupal core where user-supplied input is not properly sanitized before being rendered in web pages. This allows authenticated attackers to inject malicious JavaScript code that executes in the browsers of other users viewing the affected content.
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
< 10.5.12>= 10.6.0, < 10.6.11>= 11.0.0, < 11.2.14>= 11.3.0, < 11.3.12CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Drupal core versionAccess the Drupal administrative dashboard and navigate to Reports > Status report, or check the composer.json file in the Drupal root directory for the 'drupal/core' version entryAffected if The version falls within any of these ranges: < 10.5.12, >= 10.6.0 and < 10.6.11, >= 11.0.0 and < 11.2.14, or >= 11.3.0 and < 11.3.12
-
Verify if authenticated users can submit contentNavigate to People > Roles and Permissions in the Drupal admin panel. Check if roles other than Administrator have permissions to create or edit content types, comments, or other user-submitted dataAffected if Authenticated users have permissions to submit or edit content that gets rendered on the site
-
Confirm input filtering is not properly configuredNavigate to Configuration > Content authoring > Text formats and formats (such as Full HTML). Verify whether the format used by authenticated users has appropriate HTML filters enabled or is lacking proper sanitizationAffected if The text format assigned to authenticated users allows raw HTML input or has XSS filters disabled or misconfigured
-
Inspect rendered output for potential unsanitized contentCreate a test content item using an authenticated user account with a sample script tag in a text field (e.g., <script>alert('test')</script>), then view the page source to see if the script tag is rendered as-is rather than being escaped or strippedAffected if The script tag executes or appears unescaped in the page source when viewed by other users
A site is affected if it runs a Drupal core version within the affected ranges AND allows authenticated users to submit content through text fields without proper HTML sanitization filters in place.
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.5.1210.6.1111.2.14
Upgrade Drupal core to a patched version beyond the affected ranges (10.5.12, 10.6.11, 11.2.14, 11.3.12, or later) and audit custom modules/themes for similar unsanitized output patterns.
Drupal 11.3.12 (or appropriate branch fix: 10.5.12, 10.6.11, 11.2.14, or 11.3.12)
- 1. Identify the currently installed Drupal Core version by checking the CHANGELOG.txt file or running `drush status`
- 2. Determine which upgrade path applies based on your current version (10.5.x, 10.6.x, 11.2.x, or 11.3.x)
- 3. Backup your Drupal database and files before proceeding with any upgrade
- 4. For Drupal 10.5.x: Upgrade to version 10.5.12
- 5. For Drupal 10.6.x: Upgrade to version 10.6.11
- 6. For Drupal 11.2.x: Upgrade to version 11.2.14
- 7. For Drupal 11.3.x: Upgrade to version 11.3.12
- 8. Run database updates after upgrading using `drush updatedb` or `/update.php`
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,256.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55808 — 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-2026-55808 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