DrupalCMS
CVE-2026-6365
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: from 8.0.0 before 10.5.9, from 10.6.0 before 10.6.7, from 11.0.0 before 11.2.11, from 11.3.0 before 11.3.7.
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 confidenceCross-Site Scripting (XSS) vulnerability in Drupal core allows attackers to inject malicious scripts into web pages through improper input neutralization. The vulnerability affects multiple Drupal versions spanning 8.x, 10.x, and 11.x branches, requiring updates to specific patched versions (10.5.9, 10.6.7, 11.2.11, or 11.3.7).
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.5.9>= 10.6.0, < 10.6.7>= 11.0.0, < 11.2.11>= 11.3.0, < 11.3.7CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 versionLocate the VERSION file in the Drupal root directory, or run 'drush status' or 'composer show drupal/core' to retrieve the exact version numberAffected if The version falls within any of these ranges: >= 8.0.0 and < 10.5.9, >= 10.6.0 and < 10.6.7, >= 11.0.0 and < 11.2.11, or >= 11.3.0 and < 11.3.7
-
Check if site accepts and displays user-generated contentReview enabled modules that accept user input (such as webforms, comment modules, or custom content types) and verify whether this content is rendered in pages without additional output filteringAffected if The site processes and displays user-submitted content in web pages without proper sanitization
-
Identify publicly accessible input pathwaysAudit which Drupal forms and fields are exposed to anonymous or authenticated users, particularly those that store data for later display in page generationAffected if Untrusted user input can be submitted and subsequently rendered in output without the fixed security patch applied
You are affected if your Drupal core version is within any of the four vulnerable ranges AND your site allows users to submit content that gets rendered in generated web pages.
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.910.6.711.2.11
Update Drupal core to the patched version appropriate for the installed branch (10.5.9+, 10.6.7+, 11.2.11+, or 11.3.7+) and verify the XSS fix does not introduce regressions.
Drupal 10.6.7, 11.2.11, or 11.3.7 (latest stable in your branch)
- 1. Back up your Drupal database and files before upgrading.
- 2. Review contributed modules and themes for compatibility with the target Drupal version.
- 3. Run `composer require drupal/core:^10.6.7 --update-with-all-dependencies` (or appropriate version for your branch)
- 4. Clear Drupal cache: `drush cr` or `php core/scripts/drupal cache-clear.php`
- 5. Verify the upgrade by running database updates: `drush updatedb`
- 6. Test critical functionality on a staging environment before deploying to production.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Drupal
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6365 — 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-6365 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