Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-55805 medium CVSS 5.4

Cross-Site Scripting (XSS) in drupal/core (CVE-2026-55805)

Summary

Cross-site scripting in drupal/core (CVE-2026-55805). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0 or later.

Original description

The description as published by the source.

The Layout Builder module doesn't sufficiently sanitize block labels in certain scenarios, which can lead to a cross-site scripting (XSS) vulnerability.

This is mitigated by the fact that both the attacker and the targeted user need to be using the Layout Builder editing interface.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-55805 has been found in drupal/core.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade drupal/core to 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0 or later.
If unsure, ask your IT team or search "drupal/core CVE-2026-55805" on the vendor's site.

CVE-2026-55805 (drupal/core) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Patched: 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in drupal/core.

📍 Affected scope

Check the vendor advisory for the affected versions of drupal/core.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'drupal/core' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'drupal/core' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で drupal/core を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade drupal/core to 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0

    ステージング環境で 10.6.13, 11.3.14, 11.4.4, 11.1.0, 11.2.0, 11.3.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist drupal/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"10.6.13"}],"database_specific":{"constraint":"<10.6.13"}},{"type":"ECOSYSTEM","events":[{"introduced":"11.3.0"},{"fixed":"11.3.14"}],"database_specific":{"constraint":">=11.3.0 <11.3.14"}},{"type":"ECOSYSTEM","events":[{"introduced":"11.4.0"},{"fixed":"11.4.4"}],"database_specific":{"constraint":">=11.4.0 <11.4.4"}},{"type":"ECOSYSTEM","events":[{"introduced":"11.0.0"},{"fixed":"11.1.0"}],"database_specific":{"constraint":"11.0.*"}},{"type":"ECOSYSTEM","events":[{"introduced":"11.1.0"},{"fixed":"11.2.0"}],"database_specific":{"constraint":"11.1.*"}},{"type":"ECOSYSTEM","events":[{"introduced":"11.2.0"},{"fixed":"11.3.0"}],"database_specific":{"constraint":"11.2.*"}}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details