CVE-2025-4809
Published: 16 May 2025
Summary
CVE-2025-4809 is a high-severity Improper Restriction of Operations within the Bounds of a Memory Buffer (CWE-119) vulnerability in Tenda Ac7 Firmware. Its CVSS base score is 8.7 (High).
Operationally, ranked in the top 21.5% 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 AC7 firmware version 15.03.06.44. The flaw resides in the fromSafeSetMacFilter function of the /goform/setMacFilterCfg endpoint, where manipulation of the deviceList argument triggers the overflow. It is tracked under CWE-119, CWE-121, and CWE-787 and assigned a CVSS 4.0 score of 8.7.
An authenticated remote attacker can supply a crafted deviceList value to corrupt the stack, enabling arbitrary code execution, privilege escalation, or denial of service. The attack requires no user interaction and can be launched over the network; exploit code has already been made public.
The listed references consist of disclosure reports and the vendor site but contain no details on patches, firmware updates, or other mitigations. The associated EPSS score has remained flat at 0.0110 with no material rise since publication.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-15552
Vulnerability details
A vulnerability was found in Tenda AC7 15.03.06.44. It has been classified as critical. Affected is the function fromSafeSetMacFilter of the file /goform/setMacFilterCfg. The manipulation of the argument deviceList leads to stack-based buffer overflow. It is possible to launch the…
more
attack 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.