CVE-2025-5527
Published: 03 June 2025
Summary
CVE-2025-5527 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Tenda Rx3 Firmware. Its CVSS base score is 8.7 (High).
Operationally, ranked in the top 17.3% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis
A stack-based buffer overflow vulnerability exists in Tenda RX3 firmware version 16.03.13.11_multi_TDE01 within the save_staticroute_data function of /goform/SetStaticRouteCfg. The flaw is triggered by improper handling of the list argument supplied to the endpoint, resulting in an out-of-bounds write on the stack. It is tracked as CVE-2025-5527, carries a CVSS 4.0 score of 8.7, and is also associated with CWE-119, CWE-121, and CWE-787.
An authenticated attacker with network access can send a crafted HTTP request to the affected endpoint and achieve arbitrary code execution or a denial-of-service condition on the device. The attack requires low privileges and no user interaction, and a working exploit has already been published.
The EPSS score remains flat at 0.0170 with no material increase since disclosure. Public references include a GitHub proof-of-concept and VulDB entries, while the vendor site offers no additional mitigation guidance in the available records.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-16791
Vulnerability details
A vulnerability was found in Tenda RX3 16.03.13.11_multi_TDE01. It has been rated as critical. This issue affects the function save_staticroute_data of the file /goform/SetStaticRouteCfg. The manipulation of the argument list leads to stack-based buffer overflow. The attack may be initiated…
more
remotely. The exploit has been disclosed to the public and may be used.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Memory protections (e.g., W^X, ASLR) make exploitation of buffer-boundary violations far harder to turn into code execution.
Ongoing control assessments and code testing (static/dynamic analysis, fuzzing) surface memory buffer restriction failures, which are then remediated before release.
Managed runtimes used by platform-independent applications (e.g., JVM, CLR) enforce memory safety, preventing most buffer overflows that require direct memory manipulation.
Detects exploitation attempts that produce memory corruption, crashes, or anomalous behavior.