# silverstripe/framework SQL injection in full text search

Advisory record · `GHSA-xx4r-5265-48j6`

- **Identifiers:** `GHSA-xx4r-5265-48j6` · `PKSA-td9q-mf48-mqpm`
- **State:** Confirmed
- **Severity:** CVSS 8.8 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:** 27 May 2024
- **Updated:** 2 Dec 2024
- **Reviewed by a person:** No

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

## Affected packages

- `silverstripe/framework` (Packagist): affected `>=3.5.0-rc1, <3.5.6 || >=3.6.0-rc1, <3.6.3 || >=4.0.0-rc1, <4.0.1`; fixed in `3.5.6`, `3.6.3`, `4.0.1`

## Machine-written summary

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

> Versions of silverstripe/framework from 3.5.0-rc1 before 3.5.6, from 3.6.0-rc1 before 3.6.3, and from 4.0.0-rc1 before 4.0.1 are affected by a SQL injection flaw in full text search. The source says the 'start' querystring parameter is not escaped safely during a fulltext search, and that the flaw is less exposed in 3.5 and 3.6 because SearchForm sanitises variables first. An attacker who can send requests to a search page could inject SQL, though the source does not describe the full impact. Upgrade to silverstripe/framework 3.5.6, 3.6.3, or 4.0.1, depending on the release line in use.

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

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/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-xx4r-5265-48j6)

## Sources

- [GitHub Advisory Database: GHSA-xx4r-5265-48j6](https://github.com/advisories/GHSA-xx4r-5265-48j6)
- [OSV: GHSA-xx4r-5265-48j6](https://osv.dev/vulnerability/GHSA-xx4r-5265-48j6)
- <https://github.com/silverstripe/silverstripe-framework/commit/099a5a3c2d99ed39bdd8815e1e2790bb9351770b>
- <https://github.com/silverstripe/silverstripe-framework/commit/a8465900bdc77199176c953890ce7587045b1ea4>
- <https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2017-008-1.yaml>
- <https://github.com/silverstripe/silverstripe-framework>
- <https://www.silverstripe.org/download/security-releases/ss-2017-008>

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-xx4r-5265-48j6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-xx4r-5265-48j6/>. Everything for agents: <https://agentprime.io/llms.txt>.
