Skip to main content

Delta DVP-12SE11T CVE-2025-15359

CRITICAL
Out-of-bounds Write (CWE-787)
2025-12-30 759f5e80-c8e1-4224-bead-956d7b33c98b
9.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain OT network access to PLC
  2. Delivery
    Send crafted protocol message
  3. Exploit
    Trigger out-of-bounds memory write
  4. Execution
    Corrupt controller memory
  5. Impact
    Execute code or crash controller

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Per the provided CVSS vector (AV:N/AC:L/PR:N/UI:N), exploitation requires network reachability to the DVP-12SE11T controller with no authentication or user interaction against the affected firmware. The supplied description ('Out-of-bound memory write Vulnerability') does not name the specific protocol, service port, feature, or message type that triggers the OOB write, so the exact trigger condition must be confirmed from the Delta advisory (PCSA-2025-00022). The primary limiting factor is network exposure: DVP series PLCs are typically deployed on segmented OT/plant networks, so realistic exploitation depends on an attacker already having access to that network segment rather than direct internet reachability.

Impact

The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes a network-reachable, low-complexity, unauthenticated out-of-bounds write (CWE-787) with full confidentiality, integrity, and availability impact - the classic profile of remotely triggerable memory corruption leading to code execution or controller crash. However, several real-world-risk signals are MISSING from the provided data: no EPSS probability, no CISA KEV listing, and no POC/exploit-code indicator were supplied, so exploitation likelihood cannot be quantified from the input. There is also no SSVC decision data (exploitation status, automatable, technical impact) to cross-reference. The affected product, a Delta DVP-12SE11T PLC, is an industrial control / OT device; such controllers are frequently deployed on segmented networks and often lack authentication, which is consistent with PR:N, but it also means the AV:N 'network' reach is usually confined to an OT/plant network rather than the open internet - a nuance the raw 9.8 score does not capture. Net assessment: treat as a HIGH-severity ICS flaw warranting prompt patching where the controller is exposed, but the absence of EPSS/KEV/POC evidence means there is no confirmation of active or imminent exploitation, so the 9.8 overstates immediacy relative to likelihood for well-segmented deployments. Verify exploitability prerequisites against the Delta advisory (PCSA-2025-00022).

Exploit ScenarioDerived

An attacker with access to the OT/industrial network reachable by the DVP-12SE11T sends a crafted network message to the controller that triggers the out-of-bounds write, corrupting memory. Given AV:N/AC:L/PR:N/UI:N, this requires no authentication, user interaction, or special timing, and could result in controller crash (loss of process control/availability) or arbitrary code execution. No public exploit identified at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 05, 2026

An out-of-bounds memory write in the firmware of the Delta DVP-12SE11T programmable logic controller allows remote attackers to corrupt memory on a network-reachable device, with the supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicating no authentication or user interaction is required and full loss of confidentiality, integrity, and availability. The flaw is classified as CWE-787 (out-of-bounds write) and is reported against the DVP-12SE11T firmware with no version constraint in the CPE record, meaning all observed firmware builds of that model should be treated as affected until the vendor advisory (Delta PCSA-2025-00022) narrows the range. No public exploit code has been identified at time of analysis and the issue is not listed in CISA KEV; realistic exploitation depends on an attacker first reaching the controller on an OT/plant network segment, since the exact triggering protocol, port, or message type is not disclosed in the available data.

RemediationAI

Patch data was not supplied in the input, so consult Delta advisory PCSA-2025-00022 (https://filecenter.deltaww.com/news/download/doc/Delta-PCSA-2025-00022_DVP-12SE11T%20Multiple%20Vulnerabilities.pdf) for the vendor-designated fixed firmware build and update the DVP-12SE11T to that exact version; do not assume any specific release number until confirmed in that document. Because the flaw is network-reachable and unauthenticated per the CVSS vector, the highest-value compensating controls until firmware is updated are network-level: place DVP-12SE11T controllers behind a firewall or OT DMZ so that no engineering workstation, HMI, or business network host can reach their management/programming ports directly, and block inbound connections to PLC services from any subnet that does not strictly require them - the trade-off is that remote programming and cross-segment HMI polling will need to be routed through a jump host or VPN gateway, which may increase engineering latency. Additional practical controls include disabling or restricting any unused PLC communication services and web interfaces on the device (side effect: loss of remote diagnostics that rely on those services), segmenting PLC traffic with allow-listed source IPs or DPI-capable industrial firewalls, and monitoring for unexpected connection attempts or malformed frames targeting the controller, keeping in mind the available description does not name the vulnerable protocol so detection rules must be derived from the advisory. Where the controller is safety- or availability-critical, prioritize isolated network placement over in-place mitigation, since a memory-corruption write can cause an unplanned controller stop even without successful code execution.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is an out-of-bounds memory write (CWE-787) in Delta DVP-12SE11T PLC firmware. This weakness class occurs when software performs a write past the end (or before the start) of an allocated buffer, typically because an externally supplied length, index, or count is not validated against the destination buffer size - a pattern commonly seen in parsing routines for industrial protocol frames or configuration data. Impact for this class ranges from memory corruption and controller crash/denial of service to attacker-controlled code execution in the firmware context, consistent with the assessed High confidentiality, integrity, and availability impacts. The affected asset is identified by the CPE cpe:2.3:o:deltaww:dvp-12se11t_firmware:*:*:*:*:*:*:*:*, i.e. the operating/firmware component of the Delta DVP-12SE11T, with a wildcard version field indicating that no specific firmware build is excluded. The provided description does not identify the protocol, service, port, or message type that reaches the vulnerable write, so the precise trigger path - whether an industrial protocol request, a web/engineering interface, or some other network service - must be confirmed from Delta's PCSA-2025-00022 advisory before building targeted detection or mitigation rules.

Know when Dvp 12Se11T Firmware gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Remotely reachable PLCs commonly accept unauthenticated protocol messages (AV:N/AC:L/PR:N), and an OOB write enables memory corruption yielding code execution or controller crash (C:H/I:H/A:H).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionNVD

DVP-12SE11T - Out-of-bound memory write Vulnerability

Executive ViewAI

Why It Matters

The Delta DVP-12SE11T programmable logic controller, a widely deployed industrial control device, is affected by a critical out-of-bounds memory write vulnerability (CVE-2025-15359) that can be exploited remotely without authentication, leading to full loss of confidentiality, integrity, and availability. No vendor-released patch is identified at time of analysis, and no public exploit identified at time of analysis, but any organization with these controllers on network-reachable OT segments faces potential operational disruption and safety risks. Leadership should prioritize immediate isolation and monitoring of affected devices until a patch becomes available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include isolating affected controllers on segmented OT networks, restricting remote access via firewall rules, monitoring for anomalous network traffic, and disabling unnecessary services. Apply vendor patch when released.

Threat Intelligence Overview

EPSS Score
0.3%
Top 75% exploitable
Prevalence
Low
industry-specific Delta PLC used in industrial automation, not general IT
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
High

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Affected Products (CPE)NVD

cpe:2.3:o:deltaww:dvp-12se11t_firmware:*:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy