# CVE-2016-20027: ZKTeco ZKBioSecurity 3.0 Multiple Reflected XSS Vulnerabilities

> Attackers can execute arbitrary scripts in user browsers via reflected XSS in ZKTeco ZKBioSecurity, potentially leading to session hijacking or data theft.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Mar 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-7v59-xppj-w9h9

## What is CVE-2016-20027?

CVE-2016-20027 is a medium-severity cross-site scripting vulnerability in ZKTeco ZKBioSecurity, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ZKTeco ZKBioSecurity 3.0 contains multiple reflected cross-site scripting vulnerabilities that allow attackers to execute arbitrary HTML and script code by injecting malicious payloads through unsanitized parameters in multiple scripts. Attackers can craft malicious URLs with XSS payloads in vulnerable parameters to execute scripts in a user's browser session within the context of the affected application.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

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

## Is CVE-2016-20027 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-20027 is a medium-severity cross-site scripting vulnerability in ZKTeco ZKBioSecurity, published on 15 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2016-20027 exists.

Affected product: ZKTeco ZKBioSecurity. 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-20027/ (Markdown: https://insights.sbomify.com/CVE-2016-20027/index.md)
```

## Sources

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

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