GHSA-qcgx-7p5f-hxvr
LOWGHSA-qcgx-7p5f-hxvr is a low-severity (CVSS 3.7) Information Exposure vulnerability in statamic/cms. O3 Security confirms whether GHSA-qcgx-7p5f-hxvr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Discoverability of user password hash in Statamic CMS
Blast Radius
statamic/cms🐘statamic/cmsReal-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
Description
It was possible to confirm a single character of a user's password hash (just the hash, not the password) using a specially crafted regular expression filter in the users endpoint of the REST API. Many requests could eventually uncover the entire hash.
The hash would not be in the response, however the presence or absence of a result would confirm if the character was in the right position. It would take a long time since the API has throttling enabled by default.
Additionally, the REST API would need to be enabled, as well as the users endpoint. Both of which are disabled by default.
Resolution
Filtering by password or password hash has been disabled.
Credits
We would like to thank Thibaud Kehler for reporting the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | statamic/cms | all versions | 3.2.39 |
| 🐘Packagist | statamic/cms | ≥ 3.3.0&&< 3.3.2 | 3.3.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms. 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 statamic/cms to 3.2.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcgx-7p5f-hxvr 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-qcgx-7p5f-hxvr 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-qcgx-7p5f-hxvr. 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-qcgx-7p5f-hxvr in your dependencies?
O3 detects GHSA-qcgx-7p5f-hxvr across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.