GHSA-wpvj-hjcr-h3p2
GHSA-wpvj-hjcr-h3p2 is a Path Traversal vulnerability in cakephp/cakephp. O3 Security confirms whether GHSA-wpvj-hjcr-h3p2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
CakePHP: View::element() is missing a path containment check
Blast Radius
cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp🐘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
Impact
View::_getElementFileName() does not check that the resolved element path is within the application/plugin view template paths. When element names are created with specifically crafted user-supplied data this weakness can be leveraged to include other PHP files on the server.
Patches
Patched releases are available in 5.3.6, 5.2.13, 5.1.7, 4.6.4, and 4.5.11.
Workarounds
If developers are not using user-supplied data in element names, no action is required.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | cakephp/cakephp | ≥ 5.3.0&&< 5.3.6 | 5.3.6 |
| 🐘Packagist | cakephp/cakephp | ≥ 5.2.0&&< 5.2.13 | 5.2.13 |
| 🐘Packagist | cakephp/cakephp | ≥ 5.0.0&&< 5.1.7 | 5.1.7 |
| 🐘Packagist | cakephp/cakephp | ≥ 4.6.0&&< 4.6.4 | 4.6.4 |
| 🐘Packagist | cakephp/cakephp | all versions | 4.5.11 |
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 5.3.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wpvj-hjcr-h3p2 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-wpvj-hjcr-h3p2 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-wpvj-hjcr-h3p2. 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-wpvj-hjcr-h3p2 in your dependencies?
O3 detects GHSA-wpvj-hjcr-h3p2 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.