An unauthenticated denial-of-service vulnerability in the device's PLCnext Engineer communication interface allow an remote attacker to interrupt access via the client application. Successful exploitation prevents communication until the PLCnext service is manually restarted.
Security readout for executives and security teams
Plain-English summary
A remote, unauthenticated attacker who can reach the PLCnext Engineer communication interface may make the client application unable to communicate with the device. Service remains disrupted until PLCnext is manually restarted, creating operational downtime but no reported confidentiality or integrity impact.
Executive priority
Treat as a high-priority availability risk where affected controllers support important operations or their engineering interface is broadly reachable. Immediately confirm inventory and segmentation, obtain authoritative version guidance, and ensure safe restart procedures. Prioritize exposed or safety-relevant environments first.
Technical view
CVE-2025-41770 is a network-reachable resource-management denial of service classified as CWE-770. It requires no privileges or user interaction and has low attack complexity. CVSS 4.0 rates it 8.7 because successful exploitation causes high device availability impact while leaving confidentiality and integrity unaffected.
Likely exposure
Exposure depends on whether the PLCnext Engineer communication interface is reachable from untrusted or poorly segmented networks. The bundle names multiple Phoenix Contact controllers, but its version entries are marked “unaffected,” so the precise affected-version range cannot be established from the supplied evidence.
Exploitation context
The supplied sources do not establish active exploitation, and the CVE is not identified as being in KEV. Exploitation requires network access to the communication interface but no authentication, privileges, or user interaction. Production testing could cause an outage requiring manual service recovery.
Researcher notes
The supplied product data is internally ambiguous: products and version 2019.0.4 appear under “affected,” while every entry has defaultStatus “unaffected.” Researchers should rely on the referenced Phoenix Contact CSAF advisory for product-status semantics. No patch version, workaround, or proof of exploitation is established in the bundle.
Mitigation direction
Obtain the precise affected-version and remediation guidance from the Phoenix Contact advisory.
Restrict the PLCnext Engineer interface to authorized engineering hosts and trusted management networks.
Block unnecessary access across internet, enterprise, wireless, and third-party network boundaries.
Prepare a controlled PLCnext service-restart procedure that accounts for operational safety and availability.
Apply vendor-provided updates or mitigations after testing them in a representative environment.
Validation and detection
Inventory the named Phoenix Contact products and record their exact firmware or software versions.
Compare each asset against the vendor advisory’s authoritative affected and fixed version ranges.
Map network paths to the PLCnext Engineer interface from untrusted and lower-trust segments.
Review monitoring data for communication failures, service restarts, or unexplained engineering-client outages.
Avoid active denial-of-service testing on production operational technology.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-770 · source CWE mapping
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.