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)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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

silverstripe/taxonomy SQL Injection vulnerabilityGHSA-p2v5-xcqm-4fv6

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.

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
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

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?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works