dbcve.org
Re9000 FirmwareOperating system · Linksys

CVE-2025-5444

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 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 and classified as critical. Affected by this vulnerability is the function RP_UpgradeFWByBBS of the file /goform/RP_UpgradeFWByBBS. The manipulation of the argument type/ch/ssidhex/security/extch/pwd/mode/ip/nm/gw leads to os command injection. The attack can be launched 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 web interface function RP_UpgradeFWByBBS at /goform/RP_UpgradeFWByBBS accepts user-controlled input (type, ch, ssidhex, security, extch, pwd, mode, ip, nm, gw parameters) without proper sanitization, allowing remote attackers to execute arbitrary OS commands. The exploit is publicly available and trivially exploitable.

MitigationApply any available firmware update from Linksys immediately. If no patch is available, disable the web management interface entirely or restrict access to trusted IP addresses only via firewall rules. Consider replacing affected devices if the vendor fails to provide a fix.

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 the range extender model
    Access the device web interface or check the device label to confirm the exact model number (RE6500, RE6250, RE6300, RE6350, RE7000, or RE9000)
    Affected if The model is one of RE6500, RE6250, RE6300, RE6350, RE7000, or RE9000
  2. Check the installed firmware version
    Log into the device web interface and navigate to the Status or Administration section to view the firmware version, or use the command 'grep version /etc/os-release' or check the firmware file name if accessible
    Affected if The firmware version matches exactly: 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, or RE6500 = 1.0.013.001
  3. Confirm the vulnerable web endpoint exists
    Send an HTTP GET request to http://[device-ip]/goform/RP_UpgradeFWByBBS and check for a response (even an error response indicates the endpoint is present)
    Affected if The endpoint responds, indicating the RP_UpgradeFWByBBS handler is present on the device
  4. Verify network accessibility of the management interface
    Check if the device web interface (port 80 or 443) is accessible from untrusted networks by attempting a connection from an external host or reviewing firewall rules
    Affected if The device management web interface is reachable from networks outside the local trusted network (such as directly from the internet or an untrusted VLAN)

A user is affected if they have a RE6500, RE6250, RE6300, RE6350, RE7000, or RE9000 running the specific firmware version listed, and the device web interface is network-accessible.

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

Apply any available firmware update from Linksys immediately. If no patch is available, disable the web management interface entirely or restrict access to trusted IP addresses only via firewall rules. Consider replacing affected devices if the vendor fails to provide a fix.

Fix this in Re9000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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