CVE-2025-3546
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 was found in H3C Magic NX15, Magic NX30 Pro, Magic NX400, Magic R3010 and Magic BE18000 up to V100R014. It has been declared as critical. Affected by this vulnerability is the function FCGI_CheckStringIfContainsSemicolon of the file /api/wizard/getLanguage 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 confidenceA command injection vulnerability exists in the FCGI_CheckStringIfContainsSemicolon function within the /api/wizard/getLanguage endpoint of H3C Magic routers (NX15, NX30 Pro, NX400, R3010, BE18000) up to V100R014. An attacker with local network access can inject arbitrary shell commands through this HTTP POST handler.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 100r014<= 100r014<= 100r014<= 100r014<= 100r014CVSS 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 device modelAccess the router web interface or check the device label to confirm the exact model (NX15, NX30 Pro, NX400, R3010, or BE18000)Affected if The device is NOT one of these five models
-
Check firmware versionLog into the router admin panel and locate the firmware version in system settings or status page, or use the command 'cat /proc/version' via telnet/SSH if availableAffected if The firmware version is newer than V100R014 (for example, V100R015 or later)
-
Verify endpoint accessibilityAttempt to access the URL 'http://<router-ip>/api/wizard/getLanguage' via HTTP POST request from a device on the local networkAffected if The endpoint responds to POST requests (vulnerable endpoint is exposed)
-
Confirm local network exposureCheck if the router management interface is accessible from the local network segment (not isolated to only the router's internal processes)Affected if The router is reachable from the local network on ports 80/443
You are affected if your H3C Magic router is model NX15, NX30 Pro, NX400, R3010, or BE18000 running firmware version V100R014 or lower, and the /api/wizard/getLanguage 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.
dbcve · scopedUpgrade affected H3C Magic devices to the latest firmware version beyond V100R014 to remediate this command injection vulnerability.
Latest firmware version newer than V100R014 (check H3C support for V100R015 or later)
- 1. Identify the current firmware version on the affected H3C Magic device (Nx15, Nx30 Pro, Nx400, R3010, or Be18000)
- 2. Navigate to the H3C official support website or the device management interface
- 3. Download the latest firmware version available for your specific device model
- 4. Upload and apply the firmware update through the device's administrative interface or via TFTP/FTP as appropriate
- 5. After reboot, verify the device is running the updated firmware version
- 6. Confirm the vulnerability is addressed by testing that the /api/wizard/getLanguage endpoint no longer accepts malicious input
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3546 — 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-3546 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