CVE-2025-5147
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 Netcore NBR1005GPEV2, NBR200V2 and B6V2 up to 20250508 and classified as critical. This issue affects the function tools_ping of the file /usr/bin/network_tools. The manipulation of the argument url 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 confidenceCommand injection vulnerability in Netcore router firmware's tools_ping function within /usr/bin/network_tools. The 'url' parameter is not sanitized before being passed to a system call, allowing arbitrary command execution with the privileges of the network_tools process.
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.
-
Confirm Netcore router hardwareIdentify the device model through device labels, web interface, or SNMP. Look for 'Netcore' branding or check the manufacturer documentation.Affected if The device is a Netcore router or gateway device.
-
Locate the vulnerable binaryCheck if the file /usr/bin/network_tools exists on the device firmware or running system. This may require shell access, firmware extraction, or consulting vendor documentation.Affected if The file /usr/bin/network_tools exists on the device.
-
Verify tools_ping function presenceIf network_tools exists, verify the 'tools_ping' function is present within it. Use 'strings network_tools | grep -i ping' or 'nm network_tools' if accessible.Affected if The tools_ping function is found within network_tools.
-
Check management interface exposureDetermine if the device's web management interface (typically HTTP/HTTPS on ports 80/443 or vendor-specific ports) is accessible from untrusted networks. Review firewall rules and ACLs.Affected if The management interface is reachable from external or untrusted networks.
-
Test url parameter injection pointIf authenticated access to the management interface is available, locate the tools_ping feature and examine how the 'url' parameter is handled. Attempt to inject harmless test characters (e.g., ';echo test') into the url field to observe command execution.Affected if The url parameter in tools_ping accepts and executes injected shell commands without sanitization.
A user is affected if they operate a Netcore router with the /usr/bin/network_tools binary containing the vulnerable tools_ping function, and that function's management interface is network-accessible.
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 dataRestrict network access to the affected management interface; apply vendor firmware update when available; implement input validation on the url parameter if custom patching is undertaken.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5147 — 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-5147 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