How severe is GHSA-xwhj-pqcg-8rcr?

No CVSS score has been assigned to GHSA-xwhj-pqcg-8rcr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-xwhj-pqcg-8rcr?

GHSA-xwhj-pqcg-8rcr affects the following packages: cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xwhj-pqcg-8rcr?

Update cakephp/cakephp to 3.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwhj-pqcg-8rcr is resolved across your whole dependency graph.

How do I detect GHSA-xwhj-pqcg-8rcr 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-xwhj-pqcg-8rcr if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-xwhj-pqcg-8rcr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-xwhj-pqcg-8rcr can be triaged on real exposure rather than presence alone.

Is GHSA-xwhj-pqcg-8rcr actively exploited in the wild?

No public exploit code has been indexed for GHSA-xwhj-pqcg-8rcr 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.

When was GHSA-xwhj-pqcg-8rcr published, and has it been updated?

GHSA-xwhj-pqcg-8rcr was published on January 20, 2023 and was last updated on November 29, 2024. 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

GHSA-xwhj-pqcg-8rcr — cakephp/cakephp

Fix: cakephp/cakephp@1ea0c87

GHSA-xwhj-pqcg-8rcr is a security vulnerability in cakephp/cakephp. A fix is available for cakephp/cakephp — see the affected versions and patch details below.

CakePHP vulnerable to Cross-site Scripting in some development error pages

Published

Jan 20, 2023

Updated

Nov 29, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected

🐘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 3.4 prior to 3.4.14, 3.5 prior to 3.5.17, and 3.6 prior to 3.6.4 contains a cross-site-scripting (XSS) vulnerability in the development only missing route and duplicate named route error pages.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`cakephp/cakephp`	≥ 3.4.0&&< 3.4.14	3.4.14`composer require cakephp/cakephp:^3.4.14`
🐘Packagist	`cakephp/cakephp`	≥ 3.5.0&&< 3.5.17	3.5.17`composer require cakephp/cakephp:^3.5.17`
🐘Packagist	`cakephp/cakephp`	≥ 3.6.0&&< 3.6.4	3.6.4`composer require cakephp/cakephp:^3.6.4`

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 3.4.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xwhj-pqcg-8rcr 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-xwhj-pqcg-8rcr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-xwhj-pqcg-8rcr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

CakePHP 3.4 prior to 3.4.14, 3.5 prior to 3.5.17, and 3.6 prior to 3.6.4 contains a cross-site-scripting (XSS) vulnerability in the development only `missing route` and `duplicate named route` error pages.

O3 Security · Impact-Aware SCA

Is GHSA-xwhj-pqcg-8rcr in your dependencies?

O3 Security finds GHSA-xwhj-pqcg-8rcr across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works