Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent network access to charger LAN
-
DeliveryDiscover CHARX SEC controller
-
ExploitSend unauthenticated log-download request
-
ExecutionRetrieve restricted log files
-
PersistHarvest credentials and topology data
-
ImpactPivot to backend EVSE infrastructure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Attacker must have network adjacency to a CHARX SEC-3000/3050/3100/3150 controller (per the description's 'adjacent' wording, despite the CVSS AV:N marking - this inconsistency should be confirmed with CERT@VDE); no credentials, no user interaction, and no special device configuration are required because the log-download interface is reachable without authentication. Exploitation is limited by the requirement for layer-2 or routed-but-segment-local access, so well-segmented deployments where the controller's management interface is isolated from general operator and public networks substantially reduce realistic exposure; conversely, public-charging deployments with flat networks or exposed maintenance ports are immediately at risk. |
| Impact | CVSS 7.5 (High) is driven by Confidentiality:High with no authentication or user interaction required, but the CVSS string here (AV:N) conflicts with the description, which explicitly states an 'adjacent' attacker - typically AV:A. This discrepancy should be verified against the vendor/CERT@VDE advisory, as it materially affects exposure: AV:A limits exploitation to the same broadcast/network segment, whereas AV:N would imply internet-reachable exposure. EPSS, KEV status, and SSVC decision data were not provided, so likelihood signals are incomplete; there is no public exploit identified at time of analysis and no evidence of active exploitation. Net risk is meaningful for operators of public/semi-public EVSE infrastructure where adjacent network access is realistic (shared maintenance VLANs, exposed OT segments) but lower for well-segmented deployments. |
| Exploit ScenarioDerived | An attacker who gains a foothold on the same charging station LAN - for example via an exposed Ethernet port on a public charger cabinet, a compromised maintenance laptop, or a flat OT segment - issues an unauthenticated request to the controller's log endpoint and downloads the log files. The retrieved logs are then mined for credentials, OCPP backend URLs, session tokens, or topology data to pivot deeper into the EV charging operator's infrastructure. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 03, 2026
Information disclosure in Phoenix Contact CHARX SEC-3000/3050/3100/3150 EV charging controllers allows an unauthenticated attacker on an adjacent network to download controller log files containing restricted information. No public exploit identified at time of analysis, but the low attack complexity and lack of authentication make opportunistic abuse straightforward once an attacker reaches the same network segment. Reported via CERT@VDE under advisory VDE-2026-060.
RemediationAI
Patch status is not enumerated in the supplied data; consult VDE-2026-060 (https://certvde.com/de/advisories/VDE-2026-060/) and the corresponding CSAF JSON (https://phoenixcontact.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2026-060.json) for the vendor-released firmware version and apply it to all CHARX SEC-3000/3050/3100/3150 units. Until the patched firmware can be deployed, place the controllers behind a dedicated management VLAN and restrict layer-2/layer-3 reachability so that only known engineering workstations can talk to them - this directly mitigates the adjacent-network attack vector but will break any unmanaged maintenance workflows that rely on broad local access. Additionally, block or firewall the log-retrieval service/port at the network edge and monitor for unexpected log-download requests; the trade-off is the loss of remote diagnostic convenience for legitimate operators.
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 CHARX SEC series are charging controllers used in electric-vehicle supply equipment (EVSE) to manage ISO 15118 / OCPP communications between charge points and backend systems. The flaw maps to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), indicating the controller exposes a log-retrieval endpoint or service without enforcing authentication or authorization. Logs from such industrial/embedded controllers commonly contain device identifiers, network topology, session metadata, firmware/diagnostic data, and potentially credentials or tokens used in charging transactions - any of which can support follow-on attacks against the charging infrastructure.
Know when Charx Sec 3150 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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Primary rating from Vendor (CERTVDE) · only source for this CVE.
CVSS VectorVendor: CERTVDE
Lifecycle Timeline
1DescriptionCVE.org
It is possible for an unauthenticated adjacent attacker to download log files of the controller, which may disclose some restricted information.
Zero Day Initiative Advisories
Executive ViewAI
Phoenix Contact CHARX SEC charging controllers (models 3000/3050/3100/3150) contain an unauthenticated information disclosure vulnerability enabling attackers on the same network segment to download restricted controller logs. Organizations operating EV charging infrastructure using these devices risk operational data exposure that could reveal system configuration, performance patterns, or facilitate follow-on attacks against charging networks.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict administrative access to charging controllers through firewall rules-limit to trusted internal subnets only; (2) Disable or restrict management protocols (HTTP, SNMP, SSH) not in active use; (3) Enable all available controller-level audit logging and centralize logs to immutable storage; (4) Deploy network segmentation with VLAN isolation for charging infrastructure; (5) Monitor for suspicious connection attempts to controller management ports; (6) Contact Phoenix Contact directly for availability of configuration hardening measures or interim updates.
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-34070
GHSA-5hqw-c68q-v3hh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB