GHSA-mhpg-hpj5-73r2 — drupal/core
LOWGHSA-mhpg-hpj5-73r2 is a low-severity (CVSS 3.7) CWE-525 vulnerability in drupal/core. A fix is available for drupal/core — see the affected versions and patch details below.
Drupal core allows Exploiting Incorrectly Configured Access Control Security Levels
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-mhpg-hpj5-73r2.
EPSS Exploitation Probability
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.
How urgent is this, really
GHSA-mhpg-hpj5-73r2 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
drupal/core🐘drupal/core🐘drupal/core🐘drupal/core🐘drupal/coreReal-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
Use of Web Browser Cache Containing Sensitive Information vulnerability in Drupal Drupal core allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Drupal core: from 8.0.0 before 10.4.9, from 10.5.0 before 10.5.6, from 11.0.0 before 11.1.9, from 11.2.0 before 11.2.8, from 7.0 before 7.103.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | drupal/core | ≥ 8.0.0&&< 10.4.9 | 10.4.9composer require drupal/core:^10.4.9 |
| 🐘Packagist | drupal/core | ≥ 10.5.0&&< 10.5.6 | 10.5.6composer require drupal/core:^10.5.6 |
| 🐘Packagist | drupal/core | ≥ 11.0.0&&< 11.1.9 | 11.1.9composer require drupal/core:^11.1.9 |
| 🐘Packagist | drupal/core | ≥ 11.2.0&&< 11.2.8 | 11.2.8composer require drupal/core:^11.2.8 |
| 🐘Packagist | drupal/core | ≥ 7.0&&< 7.103 | 7.103composer require drupal/core:^7.103 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for drupal/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update drupal/core to 10.4.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mhpg-hpj5-73r2 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mhpg-hpj5-73r2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mhpg-hpj5-73r2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mhpg-hpj5-73r2 in your dependencies?
O3 Security finds GHSA-mhpg-hpj5-73r2 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.