OpenPLC_V3 contains a cross-site request forgery (CSRF) vulnerability due to missing/insufficient CSRF validation on administrative actions. An unauthenticated attacker can induce a logged-in administrator to visit a maliciously crafted link/page that triggers state-changing requests in the OpenPLC_V3 web interface, enabling unauthorized modification of PLC settings and/or upload of malicious PLC programs. The issue is reported as fixed in OpenPLC_V3 via upstream pull request #310 (referenced by CISA ICSA-25-345-10 and the CVE record).
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Cross-Site Request Forgery (CSRF) vulnerability in OpenPLC_v3 referenced by a nuclei template PR; the PR indicates the issue is fixed and a CVE has been issued.
A cross-site request forgery (CSRF) vulnerability in OpenPLC_V3 allows unauthenticated attackers to trick logged-in administrators into executing unauthorized actions, such as modifying PLC settings or uploading malicious programs, potentially causing significant disruption or damage to connected systems.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.