Skip to content
Fencer Vulns
medium 6.5

CVE-2024-40120 json

SeaweedFS Vulnerable to SQL Injection

published 2025-05-16 17 mo ago modified 2026-09-10 1 mo ago also BIT-seaweedfs-2024-40120 , EUVD-2024-54550 , GHSA-q97m-8853-pq76 , GO-2025-3690

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 18%
public exploits
0
none known

Summary

seaweedfs v3.68 was discovered to contain a SQL injection vulnerability via the component /abstract_sql/abstract_sql_store.go.

Patch / fix

  • go github.com/seaweedfs/seaweedfs 0.0.0-20240625155419-9ac102336200
  • bitnami seaweedfs 3.69.0
  • govulncheck-vulndb openSUSE Tumbleweed 0.0.20250523T151856-1.1

opensuse advisories openSUSE-SU-2025:15159-1

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
17 mo ago

Exploit prediction

0.26% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/seaweedfs/seaweedfs/issues/5710 referenced PoC, tagged "exploit" by a source, unverified
  • gist.github.com https://gist.github.com/sud0why/1b2115c1d644bd3db1c1b3f16684a78c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/seaweedfs/seaweedfs
<0.0.0-20240625155419-9ac102336200
0.0.0-20240625155419-9ac102336200
bitnami seaweedfs
>=3.68.0, <3.69.0
3.69.0

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.