dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-48890

CRITICAL · 9.8 CVSS v3.0 Published 2025-06-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
WRH-733GBK and WRH-733GWH contain an improper neutralization of special elements used in an OS command ('OS Command Injection') vulnerability in miniigd SOAP service. If a remote unauthenticated attacker sends a specially crafted request to the affected product, an arbitrary OS command may be executed.

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 confidence

OS command injection vulnerability in the miniigd SOAP service of WRH-733GBK and WRH-733GWH wireless routers allows remote unauthenticated attackers to execute arbitrary OS commands via specially crafted requests.

MitigationRestrict network access to the miniigd service; apply vendor firmware updates when available; if no patch exists, consider network segmentation or device replacement.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

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

  1. Identify device model
    Check the device label or web interface for model number WRH-733GBK or WRH-733GWH
    Affected if Device model is WRH-733GBK or WRH-733GWH
  2. Locate miniigd service
    Check running processes or network listening services for miniigd daemon; examine /var/log or system services if SSH/telnet access is available
    Affected if miniigd service is running on the device
  3. Verify miniigd network exposure
    Check router firewall settings, WAN interface bindings, or port scans from outside the LAN to determine if port 80/8080 or the SOAP service port is accessible from untrusted networks
    Affected if miniigd service is exposed to WAN or untrusted network interfaces
  4. Check for unauthenticated SOAP access
    Send a probe request to the miniigd SOAP endpoint (typically / SOAP gateway) without authentication credentials
    Affected if SOAP service accepts requests without authentication
  5. Compare firmware version
    Check router web interface or firmware image for version string; compare against any vendor release notes
    Affected if Firmware version predates any vendor security update (if available)

The device is affected if it is a WRH-733GBK or WRH-733GWH router with the miniigd SOAP service exposed to an untrusted network, allowing remote command injection without authentication.

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

Restrict network access to the miniigd service; apply vendor firmware updates when available; if no patch exists, consider network segmentation or device replacement.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48890 — 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-48890 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