CVE-2015-8379 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. O3 Security confirms whether CVE-2015-8379 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CakePHP might allow remote attackers to bypass CSRF protection mechanism via the _method parameter
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.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. 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 cakephp/cakephp to 3.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2015-8379 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 CVE-2015-8379 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 CVE-2015-8379. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2015-8379 in your dependencies?
O3 detects CVE-2015-8379 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.