CVE-2025-3542
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability, which was classified as critical, was found in H3C Magic NX15, Magic NX400 and Magic R3010 up to V100R014. This affects the function FCGI_WizardProtoProcess of the file /api/wizard/getsyncpppoecfg of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack needs to be initiated within the local network. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA command injection vulnerability exists in the HTTP POST Request Handler of H3C Magic NX15, NX400, and R3010 routers (firmware V100R014 and below). The issue is in the FCGI_WizardProtoProcess function within /api/wizard/getsyncpppoecfg, where unsanitized user input is passed to system command execution. The attack requires local network access, but a public exploit exists.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the router modelAccess the router admin panel or check the device label to confirm the exact model is H3C Magic NX15, NX400, or R3010Affected if The device is not one of these three specific models, the check does not apply
-
Check the firmware versionLog into the router web interface or use the command line (telnet/ssh if enabled) and retrieve the firmware version. Compare it to V100R014 - versions V100R014 or lower are affectedAffected if Firmware version is V100R014 or any version below V100R014 (e.g., V100R013, V100R012)
-
Verify the wizard API endpoint is accessibleFrom a device on the local network, send an HTTP POST request to http://<router-ip>/api/wizard/getsyncpppoecfg. A valid response indicates the endpoint existsAffected if The endpoint responds with any HTTP status code (200, 400, 500), meaning the vulnerable FCGI_WizardProtoProcess function is present
-
Confirm network exposure to local usersDetermine if the router management interface (HTTP/HTTPS on ports 80/443) is bound to LAN-facing interfaces and accessible to devices on the local network without additional authentication barriersAffected if The management interface is reachable from the local network without network segmentation or IP restrictions
You are affected if you own an H3C Magic NX15, NX400, or R3010 router running firmware V100R014 or below, and the /api/wizard/getsyncpppoecfg endpoint is accessible from your local network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade affected H3C Magic router firmware to the latest version beyond V100R014. If no patched firmware is available, restrict network access to the management interface and disable the wizard API endpoint if possible.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3542 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-3542 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data