CVE-2025-3545
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 classified as critical. Affected is the function FCGI_CheckStringIfContainsSemicolon of the file /api/wizard/setLanguage of the component HTTP POST Request Handler. The manipulation leads to command injection. The attack needs to be approached 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 confidenceCommand injection vulnerability in H3C Magic router web interface. The /api/wizard/setLanguage endpoint's FCGI_CheckStringIfContainsSemicolon function does not properly sanitize input, allowing arbitrary command execution via semicolon-separated commands in the POST request. Attack requires local network access.
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 H3C Magic router in your environmentCheck the device model via web interface login page, router status page, or physical device labeling. Look for 'H3C Magic' branding or check DHCP lease tables for 'H3C' or 'Magic' in device hostnames.Affected if The device is an H3C Magic router series.
-
Determine firmware versionLog into the router web interface and navigate to System Settings, Status, or About page to find the firmware version. Alternatively, check via CLI if SSH/Telnet access is available.Affected if Firmware version is earlier than V100R014 (the fixed release).
-
Verify web management interface is enabledAttempt to access the router login page on common ports 80/443 from a client on the network. Check router settings for 'Web Management' or 'HTTP/HTTPS Management' status.Affected if The web interface is enabled and responds to requests.
-
Assess network exposure of management interfaceCheck router firewall settings, access control lists, or WAN/LAN interface bindings to determine if the /api/wizard/setLanguage endpoint is reachable from untrusted networks. Review NAT port forwarding rules that may expose port 80/443 externally.Affected if The management interface is accessible from outside the local trusted network, or port forwarding rules expose it to the WAN.
Users are affected if they have an H3C Magic router with firmware before V100R014 and the router web interface is accessible from the network where the attacker resides.
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 devices to the latest firmware version beyond V100R014. Additionally, restrict network access to the management interface and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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 $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-3545 — 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-3545 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