CVE-2016-20032
Stored XSS in ZKTeco ZKAccess 5.3.1 Enables Session Hijacking
Publication date: 2026-03-16
Last updated on: 2026-03-16
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| zkteco | zkaccess_security_system | to 5.3.12252 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2016-20032 is a stored cross-site scripting (XSS) vulnerability in the ZKTeco ZKAccess Security System version 5.3.1. It occurs because the application does not properly sanitize input passed through the 'holiday_name' and 'memo' POST parameters. Attackers can inject malicious HTML or script code into these parameters, which is then stored and later executed in the context of a user's browser session when the data is viewed."}, {'type': 'paragraph', 'content': 'This vulnerability allows attackers to execute arbitrary HTML and JavaScript code, potentially compromising user sessions and enabling theft of sensitive information.'}] [1, 2, 3, 4]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "Exploitation of this stored XSS vulnerability can lead to attackers executing arbitrary scripts within the victim's browser session. This can result in session hijacking, theft of sensitive information, defacement of the web interface, or other malicious actions performed on behalf of the user."}, {'type': 'paragraph', 'content': 'Because the vulnerability is remotely exploitable via network requests and requires only low attack complexity, it poses a moderate risk to users of the affected system.'}] [1, 2, 3, 4]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by submitting crafted POST requests containing script code in the 'holiday_name' and 'memo' parameters to the affected ZKTeco ZKAccess Security System web interface and observing if the injected scripts execute in the browser context."}, {'type': 'paragraph', 'content': "A practical detection method involves sending POST requests to the endpoint `/data/iaccess/AccHolidays/_new_/?_lock=1` with malicious payloads embedded in the 'holiday_name' and 'memo' parameters and checking for script execution or JavaScript alert pop-ups."}, {'type': 'paragraph', 'content': 'For example, using curl to test the vulnerability might look like this:'}, {'type': 'list_item', 'content': 'curl -X POST -d "holiday_name=<script>alert(\'XSS\')</script>&memo=<script>alert(\'XSS\')</script>" http://[target]/data/iaccess/AccHolidays/_new_/?_lock=1'}, {'type': 'paragraph', 'content': 'If the alert pop-ups or injected scripts execute in the browser when viewing the affected page, the system is vulnerable.'}] [3, 4]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': "Immediate mitigation steps include restricting access to the affected web interface to trusted users only and disabling or limiting the ability to submit data through the vulnerable 'holiday_name' and 'memo' POST parameters."}, {'type': 'paragraph', 'content': 'Additionally, monitor and filter incoming POST requests to detect and block those containing suspicious script tags or HTML code targeting these parameters.'}, {'type': 'paragraph', 'content': 'Applying input validation and sanitization on the server side to neutralize any HTML or script code in these parameters is critical to prevent exploitation.'}, {'type': 'paragraph', 'content': 'If available, update the ZKTeco ZKAccess Security System to a version where this vulnerability is patched or contact the vendor for security updates.'}] [1, 2, 4]