GHSA-556q-h4vr-pgh2 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in cakephp/cakephp. 4 public exploit references exist, so weaponization risk is real. A fix is available for cakephp/cakephp — see the affected versions and patch details below.
CakePHP might allow remote attackers to bypass CSRF protection mechanism via the _method parameter
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-556q-h4vr-pgh2 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 379,145 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
cakephp/cakephpReal-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
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass the CSRF protection mechanism via the _method parameter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cakephp/cakephp | ≥ 2.0.0-alpha&&< 3.1.5 | 3.1.5composer require cakephp/cakephp:^3.1.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass …
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass …
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass …
CakePHP 2.x and 3.x before 3.1.5 might allow remote attackers to bypass …
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for cakephp/cakephp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update cakephp/cakephp to 3.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-556q-h4vr-pgh2 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-556q-h4vr-pgh2 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-556q-h4vr-pgh2. 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-556q-h4vr-pgh2 in your dependencies?
O3 Security finds GHSA-556q-h4vr-pgh2 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.