CHARX SEC-3150: Exposed Dangerous Method or Function
CVE-2026-44107 is a high-severity exposed dangerous method or function vulnerability in CHARX SEC-3150 from Phoenix Contact, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 1.9.1 as the first without the flaw, so updating CHARX SEC-3150 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.56% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update CHARX SEC-3150 to 1.9.1 or a later version.
- Update CHARX SEC-3100 to 1.9.1 or a later version.
- Update CHARX SEC-3050 to 1.9.1 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Phoenix Contact | CHARX SEC-3150 | 1.0.0 up to, but not including, 1.9.1 | 1.9.1 |
| Phoenix Contact | CHARX SEC-3100 | 1.0.0 up to, but not including, 1.9.1 | 1.9.1 |
| Phoenix Contact | CHARX SEC-3050 | 1.0.0 up to, but not including, 1.9.1 | 1.9.1 |
| Phoenix Contact | CHARX SEC-3000 | 1.0.0 up to, but not including, 1.9.1 | 1.9.1 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA (cert.vde.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (cert.vde.com) |
| CVSS 3.1 | 7.5 | High | CNA (cert.vde.com) |
Official description
A reboot of the charging controller can be triggered via Modbus TCP without authentication. Therefore, when the Modbus functionality is enabled by opening the port that CharxModbusServer is listening, an unauthenticated attacker can perform a Denial-of-Service attack.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Exposed Dangerous Method or Function
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
How developers prevent this class of flaw
- If you must expose a method, make sure to perform input validation on all arguments, limit access to authorized parties, and protect against all possible vulnerabilities.
- Identify all exposed functionality. Explicitly list all functionality that must be exposed to some user or set of users. Identify which functionality may be: accessible to all users restricted to a small set of privileged users prevented from being directly accessible at all Ensure that the implemented code follows these expectations. This includes setting the appropriate access modifiers where applicable (public, private, protected, etc.) or not marking ActiveX controls safe-for-scripting.
More Exposed Dangerous Method or Function vulnerabilities (CWE-749)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
References
Other references
Other vulnerabilities in CHARX SEC-3150
- 9.8 Critical severity
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.4 Critical severity
Recent Exposed Dangerous Method or Function vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 9.1 Critical severity
- 9.9 Critical severity
- 8.7 High severity
- 7.5 High severity
Spotted an error? Tell us.