# CVE-2024-32231: SQL injection in github.com/stashapp/stash

> Attackers can execute arbitrary SQL commands via the sort parameter in Stash, potentially reading or modifying database contents.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2024
- **Updated:** 22 Nov 2024
- **Also known as:** GHSA-75jf-52jg-qqh4, GO-2024-3070

## What is CVE-2024-32231?

CVE-2024-32231 is a medium-severity SQL injection vulnerability in n/a, published on 15 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Stash up to v0.25.1 was discovered to contain a SQL injection vulnerability via the sort parameter.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-32231?

3 open source packages ship an affected version, including github.com/stashapp/stash. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/stashapp/stash` | Go | All versions | 0.26.0 |
| `github.com/stashapp/stash` | Go | All versions | 0.26.0 |
| `github.com/stashapp/stash` | Go | All versions | 0.26.0 |

Products: Stashapp Stash.

## How do I fix CVE-2024-32231?

Upgrade github.com/stashapp/stash to 0.26.0 or later.

## Is CVE-2024-32231 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32231 exists.

Public exploit code:

- Stash < 0.26.0 - SQL Injection (nuclei): http/cves/2024/CVE-2024-32231.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32231 and fix it if it is affected.

What it is: CVE-2024-32231 is a medium-severity SQL injection vulnerability in n/a, published on 15 Aug 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-32231 exists.

Affected packages and fixed versions:
- github.com/stashapp/stash (Go): affected all versions; fixed in 0.26.0
- github.com/stashapp/stash (Go): affected all versions; fixed in 0.26.0
- github.com/stashapp/stash (Go): affected all versions; fixed in 0.26.0

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/CVE-2024-32231/ (Markdown: https://insights.sbomify.com/CVE-2024-32231/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32231
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32231
- OSV: https://osv.dev/vulnerability/CVE-2024-32231

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32231/
Summaries are generated and may contain mistakes; the official description above is the record.