CVE
free-fs SQL injection in share listing orderBy parameter
Affects free-fs 2.0.1 through 2.3.1. No fixed version is listed in the checked facts, and the vendor gave no severity rating.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
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
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. free-fs versions 2.0.1 through 2.3.1 are affected
- Published
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dromara free-fs contains an SQL injection flaw in its share listing endpoint, where the orderBy parameter is inserted into a database query without validation. A remote attacker who has a low-privilege login can exploit it to read arbitrary database contents, such as share codes, by using crafted ordering expressions.
Original 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.
Who should check
Teams running dromara free-fs 2.0.x through 2.3.x, where ordinary user accounts can call the share list endpoint
“Affected versions: 2.0.x through 2.3.x”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
free-fs versions 2.0.1 through 2.3.1 are affectedWorkaround: The checked facts give no workaround, so none can be stated here. The vendor's advisory is the place to look for one.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-129160 (Dromara free-fs 2.0.1 through 2.3.1 SQL Injection via orderBy Parameter), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-129160 (entry last updated 2026-11-13):
Affected:
- dromara free-fs: from 2.0.1, through 2.3.1
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- free-fs versions 2.0.1 through 2.3.1 are affected (source: https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-sql-injection-via-orderby-parameter)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129160 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129160 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/dromara/free-fs/issues/28
- https://vul.yulun.ac.cn/20261024/free-fs/
- https://github.com/dromara/free-fs/blob/f8f4ff2a0b0af8fcd5cbecbf99a4afb7d0b7c020/fs-modules/fs-file/src/main/java/com/xddcodec/fs/file/service/impl/FileShareServiceImpl.java#L93-L99
- https://www.vulncheck.com/advisories/dromara-free-fs-2.0.1-through-2.3.1-sql-injection-via-orderby-parameter
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-129160
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129160"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- dromara free-fs
From 2.0.1 · through 2.3.1
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Report
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-129160
Is CVE-2026-129160 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The orderBy parameter in free-fs can be used to inject SQL. The checked facts say this lets a reader pull data from any table in the database, including share codes and password hashes.Source: vulncheck.com, vul.yulun.ac.cn
Which versions are affected by CVE-2026-129160?
free-fs: from 2.0.1 through 2.3.1.Source: cve.now feed data
Am I affected, and how do I check?
free-fs versions 2.0.1 through 2.3.1 are listed as affected. To check a version, look at the free-fs version declared in the project's dependency or build file.Source: vulncheck.com, vul.yulun.ac.cn
How do I fix CVE-2026-129160?
The checked facts name no fixed version and no vendor patch, so no upgrade target can be given. Check the vendor's advisory for a fix.Source: vulncheck.com, vul.yulun.ac.cn
What if there's no patch?
The checked facts give no workaround, so none can be stated here. The vendor's advisory is the place to look for one.Source: vulncheck.com, vul.yulun.ac.cn