# CVE-2025-3543: Command injection in Magic NX15

> Attackers on the local network can execute arbitrary commands via a crafted HTTP POST request to the wizard configuration endpoint.

- **Severity:** High 8.6 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Apr 2025
- **Updated:** 14 Apr 2025
- **Also known as:** GHSA-77j8-wvj3-8h4c

## What is CVE-2025-3543?

CVE-2025-3543 is a high-severity command injection vulnerability in H3C Magic NX15, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in H3C Magic NX15, Magic NX30 Pro, Magic NX400 and Magic R3010 up to V100R014 and classified as critical. This vulnerability affects the function FCGI_WizardProtoProcess of the file /api/wizard/setsyncpppoecfg of the component HTTP POST Request Handler. The manipulation leads to command injection. Access to the local network is required for this attack. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2025-3543 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3543 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3543 is a high-severity command injection vulnerability in H3C Magic NX15, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-3543 exists.

Affected product: H3C Magic NX15. 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-3543/ (Markdown: https://insights.sbomify.com/CVE-2025-3543/index.md)
```

## Sources

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

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