# CVE-2026-129160: Dromara free-fs 2.0.1 through 2.3.1 SQL Injection via orderBy Parameter


- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-g8hr-rr8x-cm5q

## What is CVE-2026-129160?

CVE-2026-129160 is a high-severity vulnerability in dromara free-fs, published on 13 Nov 2026. 

### Official description

free-fs 2.0.1 through 2.3.1 contains an SQL injection vulnerability in FileShareServiceImpl.getPages, which passes the orderBy parameter of the /apis/share/pages endpoint verbatim into the ORDER BY clause via MyBatis-Flex without a column whitelist. Authenticated users can supply CASE WHEN subquery expressions that use share ordering as a boolean oracle to read arbitrary database contents, such as share codes.

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

## Which versions are affected by CVE-2026-129160?

1 open source package ship an affected version, including dromara/free-fs.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `dromara/free-fs` | GitHub | `pkg:github/dromara/free-fs` | From 2.0.1 to 2.3.1 | None |

## How do I fix CVE-2026-129160?

No fix has been published for CVE-2026-129160 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-129160 being exploited?

There is no known exploitation of CVE-2026-129160 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-129160 and fix it if it is affected.

What it is: CVE-2026-129160 is a high-severity vulnerability in dromara free-fs, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-129160 in the wild and no public exploit code.

Affected packages and fixed versions:
- dromara/free-fs (GitHub): affected from 2.0.1 up to 2.3.1; no fix listed

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

## Sources

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

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