CVE-2026-14480: OpenPLC v3 External Control of File Name or Path
No fix listed · Affected: OpenPLC · Exploitation: not established
At a glance
Higher than 50% of scored CVEs
What it isNVD
OpenPLC Runtime v3 contains an authenticated arbitrary file write vulnerability in the legacy web UI program‑upload workflow.
The application stores an attacker‑supplied filename (prog_file) directly into the Programs.File database field and later uses this value as the destination path for an uploaded file without validating or restricting the path.
Because Python os.path.join() honors attacker‑controlled absolute paths, an authenticated user can write arbitrary files anywhere writable by the OpenPLC webserver process. In the default build pipeline, all C++ source files within the OpenPLC runtime core directory are automatically compiled into the executable runtime binary.
By writing a malicious .cpp file into this directory, an authenticated attacker can escalate the arbitrary file write into arbitrary native code execution when the operator triggers a normal program compilation and runtime start.
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.20 (20 Nov)
- Not establishedNothing in the sources we check
Not seen so far: in CISA KEV · exploited (reported) · scanning observed · proof of concept public.
Weakness and public checks
- Public check
- No public nuclei template
- Weakness
- External Control of File Name or Path · File and Path Handling
Other CVEs in OpenPLC
Every published CVE for OpenPLC , by how far exploitation has gone. This one is among them.
Coverage1 article · 1 outlet
First in our coverage: CISA, 9 Jul.
- Critical OpenPLC v3 flaw lets attackers run code via file writeCISA · official notice · first in our coverage
New articles also arrive in the RSS feed.