dbcve.org
InjectionWeakness · CWE-74

CVE-2025-3539

HIGH · 8.0 CVSS v3.1 Published 2025-04-13
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 classified as critical has been found in H3C Magic NX15, Magic NX30 Pro, Magic NX400, Magic R3010 and Magic BE18000 up to V100R014. Affected is the function FCGI_CheckStringIfContainsSemicolon of the file /api/wizard/getBasicInfo of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack can only be done 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 · high confidence

A command injection vulnerability exists in H3C Magic router firmware (NX15, NX30 Pro, NX400, R3010, BE18000 up to V100R014). The issue is in the FCGI_CheckStringIfContainsSemicolon function within the /api/wizard/getBasicInfo HTTP POST request handler. An attacker on the local network can inject arbitrary OS commands through this endpoint.

MitigationUpgrade the H3C Magic router firmware to a version beyond V100R014. If immediate upgrading is not feasible, restrict access to the router's management interface to reduce the local network attack surface.

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
    Log into the router web interface (typically at 192.168.1.1) and check the status or device info page, or look for the model number on the physical device label
    Affected if Model is NX15, NX30 Pro, NX400, R3010, or BE18000
  2. Check firmware version
    In the router web interface, navigate to System Settings or Status page to find the firmware version. It may also be visible in the footer of the web UI or in a firmware upgrade section
    Affected if Firmware version is V100R014 or lower (any version up to and including V100R014)
  3. Verify vulnerable endpoint exists
    Send a POST request to http://<router-ip>/api/wizard/getBasicInfo using curl or similar tool. The endpoint exists if you receive any HTTP response (even an error response) rather than a connection timeout or 404
    Affected if The endpoint responds to POST requests (indicates the vulnerable API handler is present)
  4. Confirm semicolon parsing in API handler
    Send a POST request to /api/wizard/getBasicInfo with a semicolon character in the body (e.g., {"test":"value;echo"}). A response indicates the FCGI_CheckStringIfContainsSemicolon function is processing the input
    Affected if The endpoint accepts and processes requests containing semicolon characters without rejecting them

You are affected if you have an H3C Magic router model NX15, NX30 Pro, NX400, R3010, or BE18000 running firmware V100R014 or lower, and the /api/wizard/getBasicInfo endpoint is accessible on your local network.

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 the H3C Magic router firmware to a version beyond V100R014. If immediate upgrading is not feasible, restrict access to the router's management interface to reduce the local network attack surface.

Recommended fix Moderate confidence

Any firmware version newer than V100R014 (contact H3C support for specific fixed release number)

  1. 1. Identify the exact model of the H3C Magic router (NX15, NX30 Pro, NX400, R3010, or BE18000)
  2. 2. Access the router's web administration interface or H3C support portal
  3. 3. Navigate to the firmware update or system upgrade section
  4. 4. Download and install the latest firmware version newer than V100R014
  5. 5. After upgrade, verify the /api/wizard/getBasicInfo endpoint no longer accepts injectable semicolon characters in parameters
  6. 6. Confirm router functionality and connectivity after update
Caveat Review H3C release notes for the specific firmware version for any configuration or feature changes

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3539 — 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-3539 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