CVE-2020-36906
Unknown Unknown - Not Provided
CSRF Vulnerability in P5 FNIP-8x16A Allows Admin Takeover

Publication date: 2026-01-06

Last updated on: 2026-01-06

Assigner: VulnCheck

Description
P5 FNIP-8x16A FNIP-4xSH 1.0.20 contains a cross-site request forgery vulnerability that allows attackers to perform administrative actions without user consent. Attackers can craft malicious web pages to add new admin users, change passwords, and modify system configurations by tricking authenticated users into loading a specially crafted form.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-01-06
Last Modified
2026-01-06
Generated
2026-05-07
AI Q&A
2026-01-06
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 4 associated CPEs
Vendor Product Version / Range
p5 fnip-8x16a 1.0.11
p5 fnip-8x16a 1.0.20
p5 fnip-4xsh 1.0.11
p5 fnip-4xsh 1.0.20
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

CVE-2020-36906 is a Cross-Site Request Forgery (CSRF) vulnerability in P5 FNIP-8x16A and FNIP-4xSH relay modules (versions 1.0.11 and 1.0.20). It allows attackers to trick authenticated users into loading malicious web pages containing specially crafted forms that perform unauthorized administrative actions. These actions include adding new admin users, changing passwords, and modifying system configurations without the user's consent. The vulnerability exists because the web application fails to properly validate the authenticity of HTTP requests, enabling attackers to exploit the session of logged-in users. [1, 3, 4]


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized administrative control over the affected devices. Attackers can add new admin users, change existing admin passwords, and alter system configurations without the knowledge or consent of legitimate users. This compromises the security and integrity of the device and potentially the entire network it controls, especially in residential or commercial automation systems where these modules are deployed. It may also enable further attacks such as session hijacking or injection of malicious code due to related XSS vulnerabilities. [1, 3, 4]


How can this vulnerability be detected on my network or system? Can you suggest some commands?

Detection of this vulnerability involves monitoring for unauthorized administrative actions or suspicious HTTP requests to the device's web interface, especially POST requests to endpoints like /user.cgi that add admin users or change passwords. Since the vulnerability exploits Cross-Site Request Forgery (CSRF), checking web server logs for unexpected POST requests or unusual parameter values can help. Additionally, inspecting the device's web interface for unsanitized GET/POST parameters or signs of injected scripts may indicate exploitation attempts. Specific commands are not provided in the resources, but network administrators can use tools like curl or wget to simulate crafted POST requests to test if the device accepts unauthorized commands without proper validation. For example, sending crafted POST requests to /user.cgi to see if admin users can be added without authentication. Monitoring HTTP traffic with tools like Wireshark or using web application scanners that detect CSRF vulnerabilities can also assist in detection. [1, 3, 4]


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the affected devices' web interfaces to trusted networks only, such as internal LAN segments, and disabling remote web access if possible. Users should avoid visiting untrusted or suspicious websites while authenticated to the device's web interface to prevent CSRF exploitation. Applying any available firmware updates or patches from the vendor is recommended, although no response or patch was noted as of the advisory dates. Implementing network-level protections such as web application firewalls (WAF) to block suspicious HTTP requests and enforcing strong authentication mechanisms can reduce risk. Additionally, educating users about the risks of CSRF and encouraging them to log out from the device's web interface when not in use can help mitigate exploitation. [1, 4]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart