# SeaweedFS Vulnerable to SQL Injection

Advisory record · `GHSA-q97m-8853-pq76`

- **Identifiers:** `GHSA-q97m-8853-pq76` · `BIT-seaweedfs-2024-40120` · `CVE-2024-40120` · `GO-2025-3690`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **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:** 16 May 2025
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 16 May 2025, 15:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `github.com/seaweedfs/seaweedfs` (Go): affected `<0.0.0-20240625155419-9ac102336200`; fixed in `0.0.0-20240625155419-9ac102336200`

## Machine-written summary

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

> SeaweedFS (github.com/seaweedfs/seaweedfs) versions before 0.0.0-20240625155419-9ac102336200 are affected by a SQL injection vulnerability in the abstract_sql store component. The source gives few details about how the injection is triggered or what access an attacker needs. The fix is listed as 0.0.0-20240625155419-9ac102336200, so upgrade to that version or later.

Written 6 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

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

- **CISA KEV:** Not listed.
- **EPSS:** 0.0027, the 19th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:43 UTC: First seen by agentprime
- 31 Oct 2026, 14:43 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q97m-8853-pq76)

## Sources

- [GitHub Advisory Database: GHSA-q97m-8853-pq76](https://github.com/advisories/GHSA-q97m-8853-pq76)
- [OSV: GHSA-q97m-8853-pq76](https://osv.dev/vulnerability/GHSA-q97m-8853-pq76)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-40120>
- <https://github.com/seaweedfs/seaweedfs/issues/5710>
- <https://github.com/seaweedfs/seaweedfs/commit/9ac1023362000f6e8e58c9d278653f5926a0d90e>
- <https://gist.github.com/sud0why/1b2115c1d644bd3db1c1b3f16684a78c>
- <https://github.com/seaweedfs/seaweedfs>
- <https://github.com/seaweedfs/seaweedfs/releases/tag/3.69>

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-q97m-8853-pq76>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q97m-8853-pq76/>. Everything for agents: <https://agentprime.io/llms.txt>.
