CVE-2025-59301
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 DVP15MC11T lacks proper validation of the modbus/tcp packets and can lead to denial of service.
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 DVP15MC11T PLC does not properly validate incoming Modbus/TCP packets, allowing specially crafted packets to trigger a denial-of-service condition that renders the device unavailable.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.16.0CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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.
-
Check the DVP15MC11T firmware versionAccess the PLC via Delta's programming software (such as ISPSoft or DVPSoft) and navigate to the system information or firmware version diagnostic page. Alternatively, query the device through its web interface if available, or check the PLC's system registers for the firmware version information.Affected if The installed firmware version is below 1.16.0
-
Verify Modbus/TCP communication is enabledIn the Delta programming software, navigate to the PLC's network configuration settings and check whether the Modbus/TCP server or client function is enabled. Look for settings related to Modbus communication ports (typically port 502) and communication parameters.Affected if Modbus/TCP is enabled and configured for network communication
-
Confirm network accessibility of Modbus/TCP portPerform a network scan or use a port scanner (such as nmap) to check if port 502 (default Modbus/TCP) is open and listening on the DVP15MC11T's IP address. Verify the device is reachable from network segments that carry untrusted traffic.Affected if Port 502 is open and the device is accessible from non-dedicated/industrial-segregated network segments
A user is affected if the DVP15MC11T firmware version is below 1.16.0, Modbus/TCP is enabled, and the device can receive Modbus/TCP packets from untrusted network sources.
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.
dbcve · scoped1.16.0
Isolate the DVP15MC11T on a dedicated industrial network segment with firewall rules filtering untrusted Modbus/TCP traffic; implement deep packet inspection or deploy an industrial DMZ to broker Modbus communications and reject malformed packets.
1.16.0
- Obtain the DVP15MC11T firmware version 1.16.0 or later from Delta Electronics support (filecenter.deltaww.com)
- Follow Delta's standard firmware update procedure for the DVP15MC11T controller
- Verify the firmware version has been successfully applied after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59301 — 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-2025-59301 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