CVE-2025-25269: Local Privilege Escalation via Unauthenticated Command Injection
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Phoenix Contact CHARX SEC-3000 1.7.3; Phoenix Contact CHARX SEC-3050 1.7.3; Phoenix Contact CHARX SEC-3100 1.7.3.
Low priority for now. Upgrade to Phoenix Contact CHARX SEC-3000 1.7.3; Phoenix Contact CHARX SEC-3050 1.7.3; Phoenix Contact CHARX SEC-3100 1.7.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An unauthenticated local attacker can inject a command that is subsequently executed as root, leading to a privilege escalation.
- Published
- Jul 8, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 22th percentile
- CWE
- CWE-78
Report tools
Action score
33
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · CERTVDE
- 8.4
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| phoenixcontact | charx sec-3000 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3000_firmware |
| phoenixcontact | charx sec-3000 | cpe:2.3:h:phoenixcontact:charx_sec-3000 |
| phoenixcontact | charx sec-3050 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3050_firmware |
| phoenixcontact | charx sec-3050 | cpe:2.3:h:phoenixcontact:charx_sec-3050 |
| phoenixcontact | charx sec-3100 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3100_firmware |
| phoenixcontact | charx sec-3100 | cpe:2.3:h:phoenixcontact:charx_sec-3100 |
| phoenixcontact | charx sec-3150 firmware | cpe:2.3:o:phoenixcontact:charx_sec-3150_firmware |
| phoenixcontact | charx sec-3150 | cpe:2.3:h:phoenixcontact:charx_sec-3150 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (CERTVDE). Independent of NVD's CPE analysis and usually ahead of it.
Phoenix Contact CHARX SEC-3000
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3050
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3100
- 0.0.0 and later · before 1.7.3affected · semver
Phoenix Contact CHARX SEC-3150
- 0.0.0 and later · before 1.7.3affected · semver
Affected versions · NVD (4)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- phoenixcontact charx sec-3000 firmwarebefore 1.7.3
- phoenixcontact charx sec-3050 firmwarebefore 1.7.3
- phoenixcontact charx sec-3100 firmwarebefore 1.7.3
- phoenixcontact charx sec-3150 firmwarebefore 1.7.3
Same product
phoenixcontact: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-25270Remote Code Execution via Unauthenticated Configuration Manipulation39Monitor
- CVE-2024-6788Phoenix Contact: update feature from CHARX controller can be used to reset a low privilege user password39Monitor
- CVE-2024-26001PHOENIX CONTACT: Out of bounds write only memory access39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-24006Jul 8, 2025 · Privilege Escalation via Insecure SSH Permissions31Monitor
- ← EarlierCVE-2025-25268Jul 8, 2025 · Unauthenticated Configuration Access via Exposed API Endpoint35Monitor
- Later →CVE-2025-25271Jul 8, 2025 · OCPP Backend Configuration via Insecure Defaults35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Phoenix Contact CHARX SEC-3000 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3050 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3100 | 1.7.3 | Vendor (CNA) |
| Phoenix Contact CHARX SEC-3150 | 1.7.3 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- HT3 Labsfinder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.