OpenPLC_V3 vulnerabilities
We track 5 vulnerabilities in OpenPLC_V3 products. 5 are rated high or critical, and none are known to be exploited. The most recent was published on April 9, 2026.
Latest OpenPLC_V3 vulnerabilities
- 8.8 High severity
OpenPLC_V3: Missing Authorization
OpenPLC_V3 REST API endpoint checks for JWT presence but never verifies the caller's role. Any authenticated user with role=user can delete any other user, including administrators, by specifying their user ID or they can create new accounts with role=admin, e
- 7.5 High severity
OpenPLC_V3: Plaintext Storage of a Password
OpenPLC_V3 is vulnerable to a Plaintext Storage of a Password vulnerability that could allow an attacker to retrieve credentials and access sensitive information.
- 9.8 Critical severity
OpenPLC_V3: Initialization of a Resource with an Insecure Default
OpenPLC_V3 is vulnerable to an Initialization of a Resource with an Insecure Default vulnerability which could allow an attacker to gain access to the system by bypassing authentication via an API.
- 8.0 High severity
OpenPLC_V3: Cross-Site Request Forgery
OpenPLC_V3 is vulnerable to a cross-site request forgery (CSRF) attack due to the absence of proper CSRF validation. This issue allows an unauthenticated attacker to trick a logged-in administrator into visiting a maliciously crafted link, potentially enabling
- 7.1 High severity
OpenPLC_V3: Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
OpenPLC_V3 has a vulnerability in the enipThread function that occurs due to the lack of a return value. This leads to a crash when the server loop ends and execution hits an illegal ud2 instruction. This issue can be triggered remotely without authentication