Skip to content
Fencer Intel
medium 5.0

CVE-2024-28135 json

PHOENIX CONTACT: command injection vulnerability in the API of the CHARX Series

published 2y ago modified 4mo ago also EUVD-2024-25282

cvss
5.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.3%
EPSS 1.3% chance of exploitation in 30 days, percentile 70%
public exploits
0
none known

Summary

A low privileged remote attacker can use a command injection vulnerability in the API which performs remote code execution as the user-app user due to improper input validation. The confidentiality is partly affected.

Is CVE-2024-28135 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 Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

1.27% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 5.0 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N

Affected products

  • PHOENIX CONTACT CHARX SEC-3000
  • PHOENIX CONTACT CHARX SEC-3050
  • PHOENIX CONTACT CHARX SEC-3100
  • PHOENIX CONTACT CHARX SEC-3150
  • phoenixcontact charx_sec_3050
  • phoenixcontact charx_sec_3100
  • phoenixcontact charx_sec_3000
  • phoenixcontact charx_sec_3150

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

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.