CVE-2025-4747
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 Bohua NetDragon Firewall 1.0 and classified as critical. This issue affects some unknown processing of the file /systemstatus/ip_status.php. The manipulation of the argument subnet leads to command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used.
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 · moderate confidenceA command injection vulnerability exists in Bohua NetDragon Firewall 1.0 in the /systemstatus/ip_status.php script. The 'subnet' parameter is not properly sanitized before being used in a system command, allowing an unauthenticated remote attacker to execute arbitrary commands on the underlying operating system.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 if Bohua NetDragon Firewall is installedSearch for the product by checking common installation directories, reviewing installed software lists, or querying running services on the device. Look for processes or services named 'NetDragon' or 'Bohua'.Affected if The system has Bohua NetDragon Firewall software present
-
Determine the installed versionCheck the product's version information through its admin interface, configuration files, or by querying the installed package. Common locations include /opt/netdragon/, /usr/local/bohua/, or the firewall's web interface about page.Affected if The version is 1.0 or any version that includes the affected component
-
Locate the vulnerable scriptCheck if the file /systemstatus/ip_status.php exists on the system by searching in the web root directory of the firewall's web interface.Affected if The file ip_status.php exists in the /systemstatus/ directory
-
Verify the vulnerable parameter is accessibleTest if the /systemstatus/ip_status.php endpoint is reachable over the network on the firewall's management interface. Attempt a basic request to confirm the script responds.Affected if The script is accessible via HTTP/HTTPS and accepts the 'subnet' parameter
-
Confirm command execution is possibleReview the source code of ip_status.php if accessible, or test the subnet parameter with a benign injection attempt (e.g., adding a simple command separator) to verify if user input is passed to shell execution functions without sanitization.Affected if User-supplied input to the subnet parameter is passed to system shell functions without validation
A system is affected if it runs Bohua NetDragon Firewall version 1.0 with the /systemstatus/ip_status.php script accessible and the subnet parameter vulnerable to injection.
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 dataImmediately restrict network access to the affected interface if possible. Implement proper input validation and sanitization for the subnet parameter, using allow-lists for expected input formats rather than blacklists, and avoid passing user input to shell execution functions.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4747 — 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-4747 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