Unauthenticated OCPP backend reconfiguration via insecure defaults
Published Jul 8, 2025 · Updated Jul 22, 2025
Authentication bypass in Phoenix Contact CHARX SEC-3xxx firmware before 1.7.3 allows remote attackers to configure a new OCPP backend. The OCPP service's configuration interface uses insecure authentication defaults and accepts backend-setting changes without authentication. An attacker must reach the device from an adjacent network, and successful exploitation redirects its OCPP communications to an unauthorized backend.
Summary
What happened
Authentication bypass in Phoenix Contact CHARX SEC-3xxx firmware before 1.7.3 allows remote attackers to configure a new OCPP backend. The OCPP service's configuration interface uses insecure authentication defaults and accepts backend-setting changes without authentication. An attacker must reach the device from an adjacent network, and successful exploitation redirects its OCPP communications to an unauthorized backend.
The record
- CVE
- CVE-2025-25271
- Published
- Jul 8, 2025
- Updated
- Jul 22, 2025
- Vendor
- Phoenix Contact
- Product
- CHARX SEC-3100
- Classifications
- CWE-1188, T0866
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 8, 2025CVE publishedPublication date reported by the CVE source.
- Jul 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0.0 <1.7.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo