# GHSA-xx4r-5265-48j6: silverstripe/framework SQL injection in full text search

> Unescaped 'start' parameter in SilverStripe fulltext search allows SQL injection, enabling attackers to read or modify database contents.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2024

## What is GHSA-xx4r-5265-48j6?

GHSA-xx4r-5265-48j6 is a SQL injection vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

When performing a fulltext search in SilverStripe 4.0.0 the 'start' querystring parameter is never escaped safely. This exposes a possible SQL injection vulnerability.

The issue exists in 3.5 and 3.6 but is less vulnerable, as SearchForm sanitises these variables prior to passing to mysql.

## Which versions are affected by GHSA-xx4r-5265-48j6?

6 open source packages ship an affected version, including silverstripe/framework.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.6 |
| `silverstripe/framework` | Packagist | From 3.5.0-rc1 | 3.5.6 |
| `silverstripe/framework` | Packagist | From 3.6.0-rc1 | 3.6.3 |
| `silverstripe/framework` | Packagist | From 3.6.0-rc1 | 3.6.3 |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.1 |
| `silverstripe/framework` | Packagist | From 4.0.0-rc1 | 4.0.1 |

## How do I fix GHSA-xx4r-5265-48j6?

Upgrade silverstripe/framework to a fixed version for your release line: 3.5.6, 3.6.3 or 4.0.1.

## Is GHSA-xx4r-5265-48j6 being exploited?

There is no known exploitation of GHSA-xx4r-5265-48j6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xx4r-5265-48j6 and fix it if it is affected.

What it is: GHSA-xx4r-5265-48j6 is a SQL injection vulnerability in silverstripe/framework, published on 27 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-xx4r-5265-48j6 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.6
- silverstripe/framework (Packagist): affected from 3.5.0-rc1; fixed in 3.5.6
- silverstripe/framework (Packagist): affected from 3.6.0-rc1; fixed in 3.6.3
- silverstripe/framework (Packagist): affected from 3.6.0-rc1; fixed in 3.6.3
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.1
- silverstripe/framework (Packagist): affected from 4.0.0-rc1; fixed in 4.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-xx4r-5265-48j6/ (Markdown: https://insights.sbomify.com/GHSA-xx4r-5265-48j6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xx4r-5265-48j6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xx4r-5265-48j6/
Summaries are generated and may contain mistakes; the official description above is the record.