How severe is GHSA-wpvj-hjcr-h3p2?

No CVSS score has been assigned to GHSA-wpvj-hjcr-h3p2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-wpvj-hjcr-h3p2?

GHSA-wpvj-hjcr-h3p2 affects the following packages: cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-wpvj-hjcr-h3p2?

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.

How do I detect GHSA-wpvj-hjcr-h3p2 in my Packagist dependencies?

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.

How do I mitigate GHSA-wpvj-hjcr-h3p2 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is GHSA-wpvj-hjcr-h3p2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wpvj-hjcr-h3p2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-wpvj-hjcr-h3p2?

GHSA-wpvj-hjcr-h3p2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 18th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wpvj-hjcr-h3p2?

GHSA-wpvj-hjcr-h3p2 is classified as Path Traversal (CWE-22), CWE-98 (CWE-98). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-wpvj-hjcr-h3p2 published, and has it been updated?

GHSA-wpvj-hjcr-h3p2 was published on June 26, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CakePHP: View::element() is missing a path containment checkGHSA-wpvj-hjcr-h3p2

GHSA-wpvj-hjcr-h3p2 is a Path Traversal vulnerability in cakephp/cakephp. A fix is available for cakephp/cakephp — see the affected versions and patch details below.

Also known asCVE-2026-48820

Published

Jun 26, 2026

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wpvj-hjcr-h3p2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs18th percentile — riskier than 18% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

🐘cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp

Real-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 is a rapid development framework for PHP. In versions 4.5.11 and earlier, 4.6.0 through 4.6.3, 5.0.0 through 5.1.6, 5.2.0 through 5.2.12, and 5.3.0 through 5.3.5, 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. Patched releases are available in 5.3.6, 5.2.13, 5.1.7, 4.6.4, and 4.5.11.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`cakephp/cakephp`	≥ 5.3.0&&< 5.3.6	5.3.6`composer require cakephp/cakephp:^5.3.6`
🐘Packagist	`cakephp/cakephp`	≥ 5.2.0&&< 5.2.13	5.2.13`composer require cakephp/cakephp:^5.2.13`
🐘Packagist	`cakephp/cakephp`	≥ 5.0.0&&< 5.1.7	5.1.7`composer require cakephp/cakephp:^5.1.7`
🐘Packagist	`cakephp/cakephp`	≥ 4.6.0&&< 4.6.4	4.6.4`composer require cakephp/cakephp:^4.6.4`
🐘Packagist	`cakephp/cakephp`	all versions	4.5.11`composer require cakephp/cakephp:^4.5.11`

Detection & mitigation playbook

Open-source dependency

Detect
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 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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-wpvj-hjcr-h3p2 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works