dbcve.org
Re9000 FirmwareOperating system · Linksys

CVE-2025-5442

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-02
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
Public exploit 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
A vulnerability, which was classified as critical, has been found in Linksys RE6500, RE6250, RE6300, RE6350, RE7000 and RE9000 1.0.013.001/1.0.04.001/1.0.04.002/1.1.05.003/1.2.07.001. This issue affects the function RP_pingGatewayByBBS of the file /goform/RP_pingGatewayByBBS. The manipulation of the argument ip/nm/gw leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Critical OS command injection vulnerability in Linksys RE6500, RE6250, RE6300, RE6350, RE7000, and RE9000 range extenders. The RP_pingGatewayByBBS function in /goform/RP_pingGatewayByBBS fails to sanitize the ip, nm, and gw parameters, allowing remote attackers to inject arbitrary OS commands via the web interface.

MitigationSince the vendor did not respond and no patch is available, immediately restrict access to the device's web management interface to trusted IPs only via firewall rules, or replace these end-of-life devices with supported alternatives.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Re9000 FirmwareOperating system
Affected:= 1.0.04.002
Re6250 FirmwareOperating system
Affected:= 1.0.04.001
Re6300 FirmwareOperating system
Affected:= 1.2.07.001
Re6350 FirmwareOperating system
Affected:= 1.0.04.001
Re7000 FirmwareOperating system
Affected:= 1.1.05.003
Re6500 FirmwareOperating system
Affected:= 1.0.013.001

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.1/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 and firmware version
    Log into the range extender's web administration interface and navigate to Status or Device Information page. Alternatively, check the device label or use the 'nvram get' command via telnet/SSH if available to retrieve the firmware version.
    Affected if The device is a RE6500, RE6250, RE6300, RE6350, RE7000, or RE9000 model running the specific firmware version listed in the affected versions (RE9000: 1.0.04.002, RE6250: 1.0.04.001, RE6300: 1.2.07.001, RE6350: 1.0.04.001, RE7000: 1.1.05.003, RE6500: 1.0.013.001).
  2. Verify the web management interface is enabled
    Attempt to access the device's HTTP interface on the LAN IP address (typically 192.168.1.1 or 192.168.1.254). Check the Administration > Management or similar page to confirm web-based management is active.
    Affected if The web interface is accessible and responds to requests, which is required to reach the vulnerable /goform/RP_pingGatewayByBBS endpoint.
  3. Confirm the vulnerable endpoint exists
    Send an HTTP GET or POST request to http://[device_ip]/goform/RP_pingGatewayByBBS and observe the response. A valid endpoint will return a response (even if it returns an error). You can use curl or a browser's developer tools.
    Affected if The endpoint responds to requests, indicating the vulnerable RP_pingGatewayByBBS function is present on the device.
  4. Check network exposure of the management interface
    Determine if the device's web interface is reachable from external networks by checking port forwarding rules, WAN accessibility scans, or remote management settings (often under Administration > Remote Management). Use an external IP scan or review router firewall rules.
    Affected if The device's web management interface (port 80/443) is exposed to the internet or an untrusted network, allowing remote unauthenticated attackers to reach the vulnerable endpoint.

A user is affected if they operate a listed Linksys RE model on the specific firmware version with the web interface accessible, especially if exposed beyond the local network.

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

Since the vendor did not respond and no patch is available, immediately restrict access to the device's web management interface to trusted IPs only via firewall rules, or replace these end-of-life devices with supported alternatives.

Fix this in Re9000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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