Rx3 FirmwareOperating system · Tenda

CVE-2025-44899

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-06
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
There is a stack overflow vulnerability in Tenda RX3 V1.0br_V16.03.13.11 In the fromSetWifiGusetBasic function of the web url /goform/ WifiGuestSet, the manipulation of the parameter shareSpeed leads to stack overflow.

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 stack-based buffer overflow vulnerability exists in the Tenda RX3 router's web interface (firmware V1.0br_V16.03.13.11). The fromSetWifiGusetBasic function at /goform/WifiGuestSet fails to properly validate the length of the shareSpeed parameter before copying it to a stack buffer, allowing an attacker to overwrite return addresses and potentially achieve remote code execution.

MitigationApply vendor firmware patch when available; until then, disable the guest Wi-Fi feature or restrict administrative access to trusted IPs to reduce attack surface.

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
Rx3 FirmwareOperating system
Affected:= 16.03.13.11_multi

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 firmware version
    Log into the router web interface and navigate to System Management > Firmware Upgrade, or check the version label on the device. Alternatively, query the router's /goform/getSysInfo endpoint or check the HTTP headers on responses.
    Affected if The firmware version is exactly V1.0br_V16.03.13.11_multi (the only affected version listed).
  2. Confirm guest Wi-Fi is enabled
    Log into the router web interface and navigate to Wi-Fi Settings > Guest Wi-Fi. Check whether the guest network is turned on.
    Affected if The guest Wi-Fi feature is enabled, as the vulnerable function fromSetWifiGusetBasic processes parameters for the guest network.
  3. Verify web interface accessibility
    Attempt to access the router's web interface at port 80 or 443 from an untrusted network. Check if remote management is enabled under System Management > Remote Management.
    Affected if The /goform/WifiGuestSet endpoint is reachable from an attacker-controlled network, allowing the overflow to be triggered via the shareSpeed parameter.

You are affected if your Tenda RX3 runs firmware V1.0br_V16.03.13.11_multi AND the guest Wi-Fi feature is enabled AND the router web interface is accessible to untrusted users.

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 vendor firmware patch when available; until then, disable the guest Wi-Fi feature or restrict administrative access to trusted IPs to reduce attack surface.

Fix this in Rx3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-44899 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