CVE-2026-12819
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDelta Electronics DVP12SE PLC exposes a Modbus TCP service over a specified port without authentication or access control, permitting unauthenticated interaction with security-sensitive PLC functions.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Delta Electronics DVP12SE PLC exposes a Modbus TCP service on a specified port without any authentication or access control mechanisms. This critical vulnerability allows any unauthenticated network attacker to directly interact with security-sensitive PLC functions, potentially enabling unauthorized control of industrial processes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the PLC's model number via its web interface, console, or network banner grab on common management ports. Look for 'DVP12SE' or Delta Electronics branding.Affected if The device is a Delta Electronics DVP12SE PLC
-
Detect Modbus TCP service availabilityPerform a TCP port scan targeting ports 502 (standard Modbus) and any additional ports the PLC may use. Use 'nmap -p 502 <target>' or similar network scanner.Affected if Port 502 or the PLC's Modbus service port is open and responding
-
Verify unauthenticated Modbus accessAttempt a Modbus function code 0x04 (read input registers) or 0x03 (read holding registers) using a Modbus client (e.g., mbtget, modscan) without providing any credentials.Affected if Modbus queries return valid responses without authentication being required
-
Check for authentication configurationIf the PLC provides a configuration interface (web, serial, or management software), inspect the Modbus/TCP settings for any authentication or access control options. Look for 'authentication', 'access control', or 'security' settings.Affected if Authentication is disabled or not configurable for the Modbus service
-
Confirm network exposureReview network firewall rules or access control lists to determine if the PLC's Modbus port is accessible from untrusted network segments or the internet.Affected if The Modbus TCP port is reachable from outside the trusted industrial network
A user is affected if they operate a Delta Electronics DVP12SE PLC with Modbus TCP exposed on the network and accessible without any authentication or access control.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement network segmentation and firewall rules to isolate the PLC from untrusted networks, and apply vendor-provided security updates or configuration changes to enable authentication on the Modbus service.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-12819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data