CVE-2025-9424 is a medium severity (4.7) OS command injection flaw in Ruijie WS7204-A, affecting version 2017.06.15. No fixed version is confirmed and the vendor did not respond to the disclosure. Until a fix is confirmed, restrict who can reach the device, review the affected code path, and scan your dependencies.
What's affected
- Product: Ruijie WS7204-A
- Affected versions: 2017.06.15
- Component:
/itbox_pi/branch_import.php?a=branch_list - Parameter: the
provinceparameter - Severity: Medium, CVSS 4.7 (
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L) - Weakness classes: CWE-77, CWE-78
- Fixed version: No fixed version is confirmed and the vendor did not respond to the disclosure, so the vendor advisory or release page should be checked
The NVD description says the province parameter is passed into an operating system command without enough control. It also says the attack can be started remotely and that an exploit has been made public. The record does not list a fixed version, and the reference pages we could reach did not either.
This is device firmware. Fixes, if any, arrive as a vendor firmware image rather than a package update.
The public report we read describes the same product, file and parameter as the record, so we found no conflict in affected versions or severity between the two. Severity above is the score in the record. The advisory text itself gives no separate score.
How to check if you're exposed
Log in to the device's own management page and read the firmware version. Compare it with the affected range (2017.06.15). The record names that build, and the advisory does not say which other builds are or are not affected.
Next, find out whether the management interface is reachable from outside your network. From a machine outside the network, check whether the management port answers at all. If it does, that is the first thing to change.
Check the vendor's support page for a newer firmware image and its release notes. There is no package manager command that covers this, so the vendor page is the source of truth.
What to do now
- Find it. Work out whether Ruijie WS7204-A is installed anywhere in your estate, including test servers and old demos.
- Limit exposure. Put the application behind a VPN or an IP allowlist, or take it offline if nobody needs it.
- Look for a fix. Check the vendor's site or repository for a newer release. If none exists, ask the vendor directly and record the answer.
- Close the gap if you can. Restrict who can reach the management interface. If you control the code, stop passing user input to a shell and validate it against a strict format.
- Watch the logs. Keep web server logs for the affected path and review them for odd input.
- Scan. Run your dependency manifest through the free in-browser dependency scan to see what else is exposed.
Why it matters
OS command injection (CWE-78) happens when a program builds a shell command from request values and runs it. If the value is not controlled, the shell can be made to do more than the developer intended. On a network appliance that often means control of the device, which usually sits at a trust boundary.
The record scores this medium at 4.7, with high privileges required, which means the caller needs an administrator account first. That lowers the odds, but weak or shared management passwords are common on devices like this.
The record shows the CISA Known Exploited Vulnerabilities flag as false, and nothing we read reports use in real attacks. The NVD description does say a proof of concept is public, which lowers the effort for anyone who wants to try it. Treat it as exposed if the product is reachable.
Quick check
Is a patch available?
The record says the vendor was contacted early and did not respond, and no fixed release is named, so treat the product as unpatched until the vendor says otherwise. Check the vendor page again before you act, because this can change.
Does this CVE mean attackers are using it now?
Not according to the sources we read. The CISA KEV flag in the record is false. The NVD description does say an exploit is public, so exposure is still worth treating seriously.
Sources
- NVD record and Safeguard Gold entry for CVE-2025-9424
- Public vulnerability report for this CVE
- Other references in the record, including VulDB, could not be retrieved when we checked.
Last reviewed: 18 October 2026.
