# silverstripe/taxonomy SQL Injection vulnerability

Advisory record · `GHSA-p2v5-xcqm-4fv6`

- **Identifiers:** `GHSA-p2v5-xcqm-4fv6` · `PKSA-yzqs-p8mw-b2w1`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-89](https://cwe.mitre.org/data/definitions/89.html)
- **Tags:** [SQL injection](https://agentprime.io/advisories/tag/sql-injection.md)
- **Published:** 28 May 2024
- **Updated:** 3 Dec 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 May 2024, 17:29 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `silverstripe/taxonomy` (Packagist): affected `>=1.3.0, <1.3.1 || >=2.0.0, <2.0.1`; fixed in `1.3.1`, `2.0.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions 1.3.0 to before 1.3.1 and 2.0.0 to before 2.0.1 of silverstripe/taxonomy are vulnerable to SQL injection. The affected controller, TaxonomyDirectoryController, is disabled by default and must be enabled by a developer before the flaw can be exploited. The source does not describe what an attacker can do once it is exploited. Upgrade to version 1.3.1 or 2.0.1.

Written 4 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** No score.

## Timeline

- 31 Oct 2026, 14:28 UTC: First seen by agentprime
- 31 Oct 2026, 14:28 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-p2v5-xcqm-4fv6)

## Sources

- [GitHub Advisory Database: GHSA-p2v5-xcqm-4fv6](https://github.com/advisories/GHSA-p2v5-xcqm-4fv6)
- [OSV: GHSA-p2v5-xcqm-4fv6](https://osv.dev/vulnerability/GHSA-p2v5-xcqm-4fv6)
- <https://github.com/silverstripe/silverstripe-taxonomy/commit/01a5d9e04b993df507058aa53e6e18efc5ca405b>
- <https://github.com/silverstripe/silverstripe-taxonomy/commit/d037941e931490c33af5029c676447ed38896ee8>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/taxonomy/SS-2018-011-1.yaml>
- <https://github.com/silverstripe/silverstripe-taxonomy>
- <https://www.silverstripe.org/download/security-releases/ss-2018-011>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-p2v5-xcqm-4fv6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-p2v5-xcqm-4fv6/>. Everything for agents: <https://agentprime.io/llms.txt>.
