How severe is GHSA-ghwc-95x2-682j?

GHSA-ghwc-95x2-682j has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-ghwc-95x2-682j?

GHSA-ghwc-95x2-682j affects the following packages: drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist), drupal/core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-ghwc-95x2-682j?

Update drupal/core to 10.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghwc-95x2-682j is resolved across your whole dependency graph.

How do I detect GHSA-ghwc-95x2-682j in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-ghwc-95x2-682j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-ghwc-95x2-682j?

O3 pinpoints whether GHSA-ghwc-95x2-682j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-ghwc-95x2-682j actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-ghwc-95x2-682j, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-ghwc-95x2-682j?

GHSA-ghwc-95x2-682j has an EPSS (Exploit Prediction Scoring System) score of 88.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is GHSA-ghwc-95x2-682j in the CISA Known Exploited Vulnerabilities catalog?

Yes. GHSA-ghwc-95x2-682j (Drupal Core SQL Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2026-05-22. CISA required all US federal civilian agencies to remediate this vulnerability by 2026-05-27. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is GHSA-ghwc-95x2-682j?

GHSA-ghwc-95x2-682j is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-ghwc-95x2-682j?

A Nuclei detection template exists for GHSA-ghwc-95x2-682j, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-ghwc-95x2-682j published, and has it been updated?

GHSA-ghwc-95x2-682j was published on May 20, 2026 and was last updated on June 18, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2026-05-22 — agencies required to remediate by 2026-05-27

🐘 Packagist

GHSA-ghwc-95x2-682j

CRITICAL

Drupal Core has a SQL Injection issue

Also known asBIT-drupal-2026-9082CVE-2026-9082DRUPAL-CORE-2026-004

Published

May 20, 2026

Updated

Jun 18, 2026

Affected

6 pkgs

Patched

6 / 6

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

88.3%probability of exploitation in next 30 days

Very High Risk100th percentile+3.69%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

6 pkgs affected

🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Drupal core allows SQL Injection.

This issue affects Drupal core: from 8.9.0 before 10.4.10, from 10.5.0 before 10.5.10, from 10.6.0 before 10.6.9, from 11.0.0 before 11.1.10, from 11.2.0 before 11.2.12, from 11.3.0 before 11.3.10.

Affected Packages

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`drupal/core`	≥ 8.9.0&&< 10.4.10	10.4.10
🐘Packagist	`drupal/core`	≥ 10.5.0&&< 10.5.10	10.5.10
🐘Packagist	`drupal/core`	≥ 10.6.0&&< 10.6.9	10.6.9
🐘Packagist	`drupal/core`	≥ 11.0.0&&< 11.1.10	11.1.10
🐘Packagist	`drupal/core`	≥ 11.2.0&&< 11.2.12	11.2.12
🐘Packagist	`drupal/core`	≥ 11.3.0&&< 11.3.10	11.3.10

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52608webappsphp

Drupal Core 10.5.5 - Error-Based SQL Injection

by cardosource · Jun 1, 2026

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update drupal/core to 10.4.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-ghwc-95x2-682j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-ghwc-95x2-682j is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-ghwc-95x2-682j. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Drupal Drupal core allows SQL Injection. This issue affects Drupal core: from 8.9.0 before 10.4.10, from 10.5.0 before 10.5.10, from 10.6.0 before 10.6.9, from 11.0.0 before 11.1.10, from 11.2.0 before 11.2.12, from 11.3.0 before 11.3.10.

O3 Security · Impact-Aware SCA

Is GHSA-ghwc-95x2-682j in your dependencies?

O3 detects GHSA-ghwc-95x2-682j across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works