CVE-2025-41699— Phoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllers
Get alerts for future matching vulnerabilitiesLog in to subscribe
I. Basic Information for CVE-2025-41699
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗ Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
Phoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllers
Source: NVD (National Vulnerability Database)
Vulnerability Description
An low privileged remote attacker with an account for the Web-based management can change the system configuration to perform a command injection as root, resulting in a total loss of confidentiality, availability and integrity due to improper control of generation of code ('Code Injection').
Source: NVD (National Vulnerability Database)
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source: NVD (National Vulnerability Database)
Vulnerability Type
对生成代码的控制不恰当(代码注入)
Source: NVD (National Vulnerability Database)
Vulnerability Title
Phoenix Contact CHARX SEC-3150 代码注入漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Phoenix Contact CHARX SEC-3150是德国菲尼克斯电气（Phoenix Contact）公司的一款交流充电控制器。 Phoenix Contact CHARX SEC-3150存在代码注入漏洞，该漏洞源于低权限远程攻击者可通过基于Web的管理账户更改系统配置执行命令注入，导致代码生成控制不当，可能完全丧失机密性、可用性和完整性。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| Phoenix Contact | CHARX SEC-3150 | 0.0.0 ~ 1.7.4 | - | |
| Phoenix Contact | CHARX SEC-3100 | 0.0.0 ~ 1.7.4 | - | |
| Phoenix Contact | CHARX SEC-3050 | 0.0.0 ~ 1.7.4 | - | |
| Phoenix Contact | CHARX SEC-3000 | 0.0.0 ~ 1.7.4 | - |
II. Public POCs for CVE-2025-41699
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POCPremium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2025-41699
请登录查看更多情报信息。
Same Patch Batch · Phoenix Contact · 2025-10-14 · 6 CVEs total
| CVE-2025-41703 | 7.5 HIGH | Phoenix Contact: UPS Shutdown via Unauthenticated Modbus Command |
| CVE-2025-41705 | 6.8 MEDIUM | Phoenix Contact: WebSocket Message Interception Leaks Webfrontend Credentials |
| CVE-2025-41704 | 5.3 MEDIUM | Phoenix Contact: Unauthenticated Modbus Service DoS via Crafted Function Code |
| CVE-2025-41706 | 5.3 MEDIUM | Phoenix Contact: Webserver Denial of Service through Malformed Content-Length |
| CVE-2025-41707 | 5.3 MEDIUM | Phoenix Contact: WebSocket Handler Denial of Service |
IV. Related Vulnerabilities
Same product: CHARX SEC-3150
- CVE-2025-25271
OCPP Backend Configuration via Insecure Defaults - CVE-2025-25270
Remote Code Execution via Unauthenticated Configuration Mani - CVE-2025-25269
Local Privilege Escalation via Unauthenticated Command Injec - CVE-2025-25268
Unauthenticated Configuration Access via Exposed API Endpoin - CVE-2025-24006
Privilege Escalation via Insecure SSH Permissions
Same vendor: Phoenix Contact
- CVE-2024-43384
Phoenix Contact: Improper removal of sensitive information i - CVE-2026-22323
Cross‑Site Request Forgery in Link Aggregation Configuration - CVE-2026-22322
Stored Cross‑Site Scripting in Link Aggregation Name Handlin - CVE-2026-22321
Stack-Based Buffer Overflow in CLI Login Username Handling o - CVE-2026-22320
Stack-Based Buffer Overflow in TFTP File-Transfer Command Ha
Same weakness: CWE-94
- CVE-2026-8539
Chrome<148.0.7778.168 XSS漏洞 - CVE-2026-8634
Crabbox < v0.12.0 Environment Variable Information Disclosur - CVE-2025-15024
RCE in Yordam Informatics' Library Automation System - CVE-2026-42555
Valtimo: SpEL injection via StandardEvaluationContext allows - CVE-2026-44827
Diffusers: None.py Trust Remote Code Bypass
V. Comments for CVE-2025-41699
No comments yet