How severe is GHSA-p2v5-xcqm-4fv6?

GHSA-p2v5-xcqm-4fv6 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-p2v5-xcqm-4fv6?

GHSA-p2v5-xcqm-4fv6 affects the following packages: silverstripe/taxonomy (Packagist), silverstripe/taxonomy (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p2v5-xcqm-4fv6?

Update silverstripe/taxonomy to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2v5-xcqm-4fv6 is resolved across your whole dependency graph.

How do I detect GHSA-p2v5-xcqm-4fv6 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/taxonomy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-p2v5-xcqm-4fv6 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-p2v5-xcqm-4fv6?

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

Is GHSA-p2v5-xcqm-4fv6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p2v5-xcqm-4fv6 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-p2v5-xcqm-4fv6 published, and has it been updated?

GHSA-p2v5-xcqm-4fv6 was published on May 28, 2024 and was last updated on December 3, 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

HIGH severity

GHSA-p2v5-xcqm-4fv6 — silverstripe/taxonomy

HIGHFix: silverstripe/silverstripe-taxonomy@01a5d9e

GHSA-p2v5-xcqm-4fv6 is a high-severity (CVSS 7.5) vulnerability in silverstripe/taxonomy. A fix is available for silverstripe/taxonomy — see the affected versions and patch details below.

silverstripe/taxonomy SQL Injection vulnerability

Published

May 28, 2024

Updated

Dec 3, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Dec 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘silverstripe/taxonomy🐘silverstripe/taxonomy

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

There is a vulnerability in silverstripe/taxonomy module that allows SQL injection. This affected controller (TaxonomyDirectoryController) is disabled by default and must be enabled by a developer for the exploit to be possible.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`silverstripe/taxonomy`	≥ 1.3.0&&< 1.3.1	1.3.1`composer require silverstripe/taxonomy:^1.3.1`
🐘Packagist	`silverstripe/taxonomy`	≥ 2.0.0&&< 2.0.1	2.0.1`composer require silverstripe/taxonomy:^2.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/taxonomy, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update silverstripe/taxonomy to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p2v5-xcqm-4fv6 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-p2v5-xcqm-4fv6 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-p2v5-xcqm-4fv6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

There is a vulnerability in silverstripe/taxonomy module that allows SQL injection. This affected controller (`TaxonomyDirectoryController`) is disabled by default and must be enabled by a developer for the exploit to be possible.

O3 Security · Impact-Aware SCA

Is GHSA-p2v5-xcqm-4fv6 in your dependencies?

O3 Security finds GHSA-p2v5-xcqm-4fv6 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