GHSA-g2vx-8v47-4vhh
GHSA-g2vx-8v47-4vhh is a Improper Input Validation vulnerability in cakephp/cakephp. 5 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-g2vx-8v47-4vhh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CakePHP allows remote attackers to modify internal Cake cache and execute arbitrary code
Blast Radius
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
The _validatePost function in libs/controller/components/security.php in CakePHP 1.3.x through 1.3.5 and 1.2.8 allows remote attackers to modify the internal Cake cache and execute arbitrary code via a crafted data[_Token][fields] value that is processed by the unserialize function, as demonstrated by modifying the file_map cache to execute arbitrary local files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cakephp/cakephp | ≥ 1.2.8&&< 1.3.6 | 1.3.6 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
CakePHP 1.3.5/1.2.8 - Cache Corruption (Metasploit)
by Metasploit · Jan 14, 2011
CakePHP 1.3.5/1.2.8 - 'Unserialize()' File Inclusion
by felix · Jan 18, 2011
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 1.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g2vx-8v47-4vhh 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-g2vx-8v47-4vhh 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-g2vx-8v47-4vhh. 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-g2vx-8v47-4vhh in your dependencies?
O3 detects GHSA-g2vx-8v47-4vhh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.