Drupal Configuration Split Cross-Site Request Forgery (CSRF) vulnerabilityGHSA-qq45-cqhg-jwx5
MEDIUMGHSA-qq45-cqhg-jwx5 is a medium-severity (CVSS 6.8) Cross-Site Request Forgery (CSRF) vulnerability in drupal/config_split. A fix is available for drupal/config_split — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-qq45-cqhg-jwx5.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
drupal/config_split🐘drupal/config_splitReal-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
Cross-Site Request Forgery (CSRF) vulnerability in Drupal Configuration Split allows Cross Site Request Forgery. This issue affects Configuration Split: from 0.0.0 before 1.10.0, from 2.0.0 before 2.0.2.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/config_split | all versions | 1.10.0composer require drupal/config_split:^1.10.0 |
| 🐘Packagist | drupal/config_split | ≥ 2.0.0&&< 2.0.2 | 2.0.2composer require drupal/config_split:^2.0.2 |
Affected Products
configuration splitnuvoleDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/config_split, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/config_split to 1.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qq45-cqhg-jwx5 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.
Frequently Asked Questions
Is GHSA-qq45-cqhg-jwx5 in your dependencies?
Find it across Packagist, including transitive dependencies.