CVE-2025-41699 json
Phoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllers
published last yr. modified 22d ago also EUVD-2025-34144
- cvss
- 8.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
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').
Patch / fix
- Phoenix Contact CHARX SEC-3150 1.7.4
- Phoenix Contact CHARX SEC-3100 1.7.4
- Phoenix Contact CHARX SEC-3050 1.7.4
- Phoenix Contact CHARX SEC-3000 1.7.4
Is CVE-2025-41699 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- last yr.
Exploit prediction
0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected products
- Phoenix Contact CHARX SEC-3150
- Phoenix Contact CHARX SEC-3100
- Phoenix Contact CHARX SEC-3050
- Phoenix Contact CHARX SEC-3000
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
References
Sources
- CVE List CVE-2025-41699
- NVD CVE-2025-41699
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.