# GHSA-xc69-p8fc-m6m5: silverstripe/subsites Unsafe SQL Query Construction (Safe Data Source)

> A potential SQL injection vulnerability in the SilverStripe subsites module allows attackers to manipulate database queries, requiring an upgrade to the fixed version.

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

## What is GHSA-xc69-p8fc-m6m5?

GHSA-xc69-p8fc-m6m5 is a SQL injection vulnerability in silverstripe/subsites, published on 28 May 2024. It can be exploited over the network.

### Official description

There is a low level potential SQL injection vulnerability in the silverstripe/subsites module has been identified and fixed in version 2.1.1.

## Which versions are affected by GHSA-xc69-p8fc-m6m5?

2 open source packages ship an affected version, including silverstripe/subsites.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `silverstripe/subsites` | Packagist | From 2.0.0 | 2.1.1 |
| `silverstripe/subsites` | Packagist | From 2.0.0 | 2.1.1 |

## How do I fix GHSA-xc69-p8fc-m6m5?

Upgrade silverstripe/subsites to 2.1.1 or later.

## Is GHSA-xc69-p8fc-m6m5 being exploited?

There is no known exploitation of GHSA-xc69-p8fc-m6m5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-xc69-p8fc-m6m5 and fix it if it is affected.

What it is: GHSA-xc69-p8fc-m6m5 is a SQL injection vulnerability in silverstripe/subsites, published on 28 May 2024. It can be exploited over the network.
Exploitation: There is no known exploitation of GHSA-xc69-p8fc-m6m5 in the wild and no public exploit code.

Affected packages and fixed versions:
- silverstripe/subsites (Packagist): affected from 2.0.0; fixed in 2.1.1
- silverstripe/subsites (Packagist): affected from 2.0.0; fixed in 2.1.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-xc69-p8fc-m6m5/ (Markdown: https://insights.sbomify.com/GHSA-xc69-p8fc-m6m5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-xc69-p8fc-m6m5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-xc69-p8fc-m6m5/
Summaries are generated and may contain mistakes; the official description above is the record.