# CVE-2025-5743: Command injection in EVLink WallBox

> An authenticated user can execute arbitrary OS commands on the EVLink WallBox by modifying web server configuration parameters.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2025
- **Updated:** 7 Oct 2025
- **Also known as:** GHSA-jqqm-2p4m-968q

## What is CVE-2025-5743?

CVE-2025-5743 is a high-severity command injection vulnerability in Schneider Electric EVLink WallBox, published on 10 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
vulnerability exists that could cause remote control over the charging station when an authenticated user
modifies configuration parameters on the web server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2025-5743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5743 is a high-severity command injection vulnerability in Schneider Electric EVLink WallBox, published on 10 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-5743 in the wild and no public exploit code.

Affected product: Schneider Electric EVLink WallBox. 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-5743/ (Markdown: https://insights.sbomify.com/CVE-2025-5743/index.md)
```

## Sources

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

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