dbcve.org
InjectionWeakness · CWE-74

CVE-2025-5146

MEDIUM · 6.3 CVSS v3.1 Published 2025-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in Netcore NBR1005GPEV2, B6V2, COVER5, NAP830, NAP930, NBR100V2 and NBR200V2 up to 20250508 and classified as critical. This vulnerability affects the function passwd_set of the file /usr/bin/routerd of the component HTTP Header Handler. The manipulation of the argument pwd leads to command injection. The attack can 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 · high confidence

A command injection vulnerability exists in the passwd_set function of the /usr/bin/routerd binary in multiple Netcore router models (NBR1005GPEV2, B6V2, COVER5, NAP830, NAP930, NBR100V2, NBR200V2). The function fails to properly sanitize the pwd argument passed through the HTTP header handler, allowing remote attackers to inject and execute arbitrary OS commands via crafted HTTP requests.

MitigationImmediately restrict network access to the device management interface, disable remote administration if feasible, and apply vendor firmware patches when released. Network segmentation can reduce exposure while awaiting patches.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Netcore router model
    Access the device admin interface or check the device label/firmware to confirm the exact model (NBR1005GPEV2, B6V2, COVER5, NAP830, NAP930, NBR100V2, or NBR200V2)
    Affected if The device model matches one of the affected models listed in the CVE
  2. Verify the routerd binary exists
    Check for the presence of /usr/bin/routerd on the device filesystem (via SSH, telnet, or firmware extraction)
    Affected if The binary /usr/bin/routerd exists on the device
  3. Confirm remote management is accessible
    Determine if the HTTP management interface is exposed to untrusted networks by checking firewall rules, WAN accessibility of the admin port, or remote admin settings in the router configuration
    Affected if The router web admin interface is reachable from outside the local network or from untrusted interfaces
  4. Check for the passwd_set endpoint exposure
    Send a crafted HTTP request to the routerd service targeting the passwd_set function with a test parameter in the pwd argument, or inspect HTTP handler logs if available
    Affected if The passwd_set function handles HTTP requests without sanitizing the pwd parameter (requires access to device logs or vulnerability scanning)
  5. Review HTTP service banner and version
    Query the HTTP service running on the router (typically ports 80 or 443 on the management interface) and capture the service banner or response headers
    Affected if The HTTP service responds on the management interface and can be reached remotely

A user is affected if they own a Netcore router model listed in the CVE, the /usr/bin/routerd binary is present, and the device management interface is accessible remotely (especially from WAN/untrusted networks) allowing injection through the passwd_set function's pwd parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately restrict network access to the device management interface, disable remote administration if feasible, and apply vendor firmware patches when released. Network segmentation can reduce exposure while awaiting patches.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5146 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5146 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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