How severe is GHSA-6hg4-vp5q-47mw?

No CVSS score has been assigned to GHSA-6hg4-vp5q-47mw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-6hg4-vp5q-47mw?

GHSA-6hg4-vp5q-47mw affects the following packages: cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist), cakephp/cakephp (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-6hg4-vp5q-47mw?

Update cakephp/cakephp to 2.0.99 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hg4-vp5q-47mw is resolved across your whole dependency graph.

How do I detect GHSA-6hg4-vp5q-47mw 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-6hg4-vp5q-47mw 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-6hg4-vp5q-47mw?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-6hg4-vp5q-47mw can be triaged on real exposure rather than presence alone.

Is GHSA-6hg4-vp5q-47mw actively exploited in the wild?

No public exploit code has been indexed for GHSA-6hg4-vp5q-47mw 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-6hg4-vp5q-47mw published, and has it been updated?

GHSA-6hg4-vp5q-47mw 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-6hg4-vp5q-47mw — cakephp/cakephp

Fix: cakephp/cakephp@056f24a

GHSA-6hg4-vp5q-47mw is a security vulnerability in cakephp/cakephp. A fix is available for cakephp/cakephp — see the affected versions and patch details below.

CakePHP allows direct access of prefixed controller actions

Published

Jan 20, 2023

Updated

Nov 29, 2024

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

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

Real-World Exposure

8 pkgs affected

🐘cakephp/cakephp🐘cakephp/cakephp🐘cakephp/cakephp🐘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

Unconventional URL paths would allow direct access to prefixed actions without setting the correct request parameters.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`cakephp/cakephp`	≥ 2.0.0&&< 2.0.99	2.0.99`composer require cakephp/cakephp:^2.0.99`
🐘Packagist	`cakephp/cakephp`	≥ 2.1.0&&< 2.1.99	2.1.99`composer require cakephp/cakephp:^2.1.99`
🐘Packagist	`cakephp/cakephp`	≥ 2.2.0&&< 2.2.99	2.2.99`composer require cakephp/cakephp:^2.2.99`
🐘Packagist	`cakephp/cakephp`	≥ 2.3.0&&< 2.3.99	2.3.99`composer require cakephp/cakephp:^2.3.99`
🐘Packagist	`cakephp/cakephp`	≥ 2.4.0&&< 2.4.99	2.4.99`composer require cakephp/cakephp:^2.4.99`
🐘Packagist	`cakephp/cakephp`	≥ 2.5.0&&< 2.5.9	2.5.9`composer require cakephp/cakephp:^2.5.9`

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 2.0.99 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6hg4-vp5q-47mw 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-6hg4-vp5q-47mw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-6hg4-vp5q-47mw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Unconventional URL paths would allow direct access to prefixed actions without setting the correct request parameters.

O3 Security · Impact-Aware SCA

Is GHSA-6hg4-vp5q-47mw in your dependencies?

O3 Security finds GHSA-6hg4-vp5q-47mw 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