# CVE-2016-20032: ZKTeco ZKAccess Security System 5.3.1 Stored XSS

> Attackers can inject malicious scripts via holiday and memo fields to steal user sessions and sensitive data in ZKTeco ZKAccess.

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

## What is CVE-2016-20032?

CVE-2016-20032 is a medium-severity cross-site scripting vulnerability in ZKTeco ZKAccess Security System, published on 15 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

ZKTeco ZKAccess Security System 5.3.1 contains a stored cross-site scripting vulnerability that allows attackers to execute arbitrary HTML and script code by injecting malicious payloads through the 'holiday_name' and 'memo' POST parameters. Attackers can submit crafted requests with script code in these parameters to compromise user browser sessions and steal sensitive information.

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

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


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

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

## Is CVE-2016-20032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-20032 is a medium-severity cross-site scripting vulnerability in ZKTeco ZKAccess Security System, published on 15 Mar 2026. Any signed-in user can exploit it over the network, 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-20032 exists.

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

## Sources

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

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