Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach device MQTT broker over network
-
DeliverySend crafted message with malicious ID
-
ExploitBroker accepts unauthenticated input
-
ExecutionNew system configuration entry created
-
ImpactIntegrity and availability loss on charger
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V14 - Data Protection Trust boundary enforcement
|
| Exploitation Conditions | Exploitation requires network reachability to the CHARX SEC controller's MQTT broker interface; the attacker POSTs a malicious ID which is accepted and written as a new system configuration entry. Per the CVSS vector (AV:N/AC:L/AT:N/PR:N/UI:N), no authentication, no user interaction, and no special attack requirements are needed against affected firmware (1.0.0 through 1.9.0). The primary limiting factor is exposure of the MQTT broker: if the broker is segmented on an isolated OT network and not reachable from untrusted hosts, remote exploitation is prevented; only devices whose broker port is accessible to the attacker are at risk. |
| Impact | The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N, VC:N/VI:H/VA:H) describes a network-reachable, low-complexity, unauthenticated attack with high integrity and availability impact but no confidentiality impact, scoring 8.8 (High) - consistent with the description of configuration tampering rather than data theft. Note a labeling inconsistency: the intelligence tag reads 'Information Disclosure,' yet both the CVSS vector (VC:N) and the description indicate integrity/availability impact, not confidentiality, so the tag appears mislabeled and should be treated with caution. There is no EPSS score, no KEV listing, and no POC in the provided data, so real-world exploitation pressure cannot be quantified; however, the combination of no authentication, network vector, and a vendor-confirmed patch makes this a genuine priority for exposed devices, since exploitation depends only on network reachability of the MQTT broker. |
| Exploit ScenarioDerived | An attacker with network access to a CHARX SEC controller's MQTT broker sends a crafted message containing a malicious ID, which the device accepts without authentication and writes as a new system configuration entry, corrupting device state and potentially disrupting charging availability. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, this needs only reachability to the broker and no credentials, user interaction, or complex preconditions. No public POC is identified at this time. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Unauthenticated configuration injection in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers (versions 1.0.0 through 1.9.0) lets a remote attacker POST a malicious ID to the device's MQTT broker and thereby create a new entry in the system configuration, causing integrity and availability loss. Reported by CERT@VDE (advisory VDE-2026-008), the flaw carries a CVSS 4.0 base score of 8.8 and requires no authentication or user interaction. No public exploit has been identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
Vendor-released patch: firmware version 1.9.1 - upgrade all CHARX SEC-3000, SEC-3050, SEC-3100, and SEC-3150 controllers from any 1.0.0-1.9.0 release to 1.9.1 or later as the primary fix, per CERT@VDE advisory VDE-2026-008 (https://www.certvde.com/en/advisories/VDE-2026-008/). Where immediate patching is not possible, restrict network reachability of the MQTT broker port by placing the controllers on an isolated OT/charging network segment and firewalling the broker so only trusted management hosts can connect, which prevents unauthenticated external POSTs at the cost of requiring any legitimate remote-management tooling to be explicitly allowlisted; also monitor for unexpected new system configuration entries as a detection compensating control. Avoid exposing the MQTT interface directly to the internet or untrusted LANs.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected devices are Phoenix Contact CHARX SEC series AC/EV charge controllers, which expose an MQTT broker used for internal message passing and device orchestration. The root cause is classified as CWE-501 (Trust Boundary Violation): data arriving on the MQTT interface from an untrusted, unauthenticated source is treated as trusted and allowed to cross into the system configuration store. Because a crafted MQTT message carrying a malicious ID is accepted without validating the sender's trust level, the attacker's input is persisted as a legitimate configuration entry, blurring the boundary between externally-supplied data and trusted internal state.
Know when the next one hits your stack
- 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
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Unauthenticated network POST to the MQTT broker (AV:N/AC:L/PR:N/UI:N) writes config with no confidentiality impact (C:N) but high integrity and availability loss (I:H/A:H).
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
Lifecycle Timeline
2DescriptionCVE.org
An unauthenticated remote attacker can post a malicious ID to the MQTT Broker results in the creation of a new configuration entry in the system configuration. This may lead to integrity and availability loss.
Zero Day Initiative Advisories
Executive ViewAI
Phoenix Contact's CHARX SEC EV charging controllers (versions 1.0.0-1.9.0) contain a vulnerability enabling unauthenticated remote access to modify system configuration, creating direct risk to charging infrastructure availability and service integrity. Any organization operating these devices faces potential service disruption and operational control loss without immediate action. Vendor patches are available and deployment should be prioritized within this month.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-51026
GHSA-pwf7-5xmc-7x99
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB