# CVE-2025-41699: Phoenix Contact: Security Advisory for CHARX SEC-3xxx charging controllers

> A low-privileged remote attacker can inject commands to execute code as root on Phoenix Contact CHARX SEC charging controllers.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-5whr-v2mg-4xrv

## What is CVE-2025-41699?

CVE-2025-41699 is a high-severity command injection vulnerability in Phoenix Contact CHARX SEC-3000, published on 14 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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').

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2025-41699?


## How do I fix CVE-2025-41699?

No fix has been published for CVE-2025-41699 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-41699 being exploited?

There is no known exploitation of CVE-2025-41699 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41699 and fix it if it is affected.

What it is: CVE-2025-41699 is a high-severity command injection vulnerability in Phoenix Contact CHARX SEC-3000, published on 14 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41699 in the wild and no public exploit code.

Affected product: Phoenix Contact CHARX SEC-3000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41699/ (Markdown: https://insights.sbomify.com/CVE-2025-41699/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41699
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41699
- OSV: https://osv.dev/vulnerability/CVE-2025-41699

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41699/
Summaries are generated and may contain mistakes; the official description above is the record.