dbcve.org
InjectionWeakness · CWE-74

CVE-2025-3543

HIGH · 8.0 CVSS v3.1 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Zero-click

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 · unedited
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.

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 · high confidence

Command injection vulnerability in H3C Magic router series (NX15, NX30 Pro, NX400, R3010 up to V100R014) allows remote attackers to execute arbitrary OS commands via the HTTP POST handler in /api/wizard/setsyncpppoecfg. The FCGI_WizardProtoProcess function fails to properly sanitize user input before passing it to system commands.

MitigationUpgrade affected H3C Magic routers to a firmware version beyond V100R014. Since local network access is required, also restrict administrative interfaces to trusted networks and implement network segmentation.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify router model
    Access the router admin web interface or check the device label. Confirm the model is one of: NX15, NX30 Pro, NX400, or R3010.
    Affected if The device is not one of the four listed H3C Magic models.
  2. Check firmware version
    In the router admin panel, navigate to System Settings or Status page to view the firmware version. Compare it against V100R014.
    Affected if The firmware version is V100R014 or lower.
  3. Verify vulnerable API endpoint exists
    Send an HTTP POST request to http://<router-ip>/api/wizard/setsyncpppoecfg. A response (even an error) indicates the endpoint exists.
    Affected if The endpoint responds, indicating the vulnerable API is present.
  4. Assess admin interface exposure
    Determine if the router admin web interface (HTTP/HTTPS on ports 80/443 or the router LAN IP) is accessible from untrusted networks or the internet.
    Affected if The admin interface is exposed to untrusted networks or the internet without network restrictions.

You are affected if you own an H3C Magic NX15, NX30 Pro, NX400, or R3010 router running firmware V100R014 or lower, with the /api/wizard/setsyncpppoecfg endpoint accessible to untrusted attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade affected H3C Magic routers to a firmware version beyond V100R014. Since local network access is required, also restrict administrative interfaces to trusted networks and implement network segmentation.

Recommended fix Moderate confidence

Firmware version newer than V100R014 (check H3C official support for exact latest release - look for V100R015 or later)

  1. 1. Identify the exact model of H3C Magic router (NX15, NX30 Pro, NX400, or R3010) from the device label or web interface
  2. 2. Visit the official H3C support website (www.h3c.com or zhiliao.h3c.com) and navigate to the downloads/support page for your specific model
  3. 3. Locate the firmware download section and look for a version newer than V100R014
  4. 4. Download the firmware file - typically a .bin or .bin file with version notation (e.g., V100R015 or later)
  5. 5. Access the router's web administration interface by entering the router's local IP address (commonly 192.168.0.1 or 192.168.1.1) in a web browser
  6. 6. Navigate to the Administration or System Settings section, then look for Firmware Upgrade or System Update
  7. 7. Upload the downloaded firmware file and initiate the upgrade process
  8. 8. Wait for the upgrade to complete - do not power off the device during this process
Caveat Firmware upgrades on consumer routers may reset configuration to defaults; back up current settings before upgrading and reconfigure after

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3543 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3543 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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