# CVE-2016-20096: Linknat VOS3000/VOS2009 2.1.2.0 SQL Injection via login.jsp

> Remote attackers can inject SQL via the login form to extract plaintext credentials and database content with DBA privileges.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-36f2-4m9x-c736

## What is CVE-2016-20096?

CVE-2016-20096 is a critical SQL injection vulnerability in Kunshi Network Technology Co., Ltd. Linknat VOS2009, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Linknat VOS3000 and VOS2009 through version 2.1.2.0 contain an unauthenticated SQL injection vulnerability that allows remote attackers to execute arbitrary SQL commands by manipulating the name parameter in a POST request to the login endpoint. Attackers can inject malicious SQL through the login form and retrieve injected query results from a subsequent session request, enabling extraction of plaintext credentials and other database content with DBA-level privileges.

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

## Which versions are affected by CVE-2016-20096?


## How do I fix CVE-2016-20096?

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

## Is CVE-2016-20096 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-20096 and fix it if it is affected.

What it is: CVE-2016-20096 is a critical SQL injection vulnerability in Kunshi Network Technology Co., Ltd. Linknat VOS2009, published on 21 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20096 exists.

Affected product: Kunshi Network Technology Co., Ltd. Linknat VOS2009. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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