CVE-2024-48712: TP-Link TL-WDR7660 · Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 15 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
To mitigate this vulnerability, organizations should immediately restrict access to the router's management interfaces to trusted networks and devices only, using network segmentation and firewall rules. Disabling remote management features or limiting them to secure VPN connections can reduce exposure. Monitoring network traffic for unusual or malformed packets targeting the router's management functions may help detect exploitation attempts. Since no patches are currently available, users should regularly check TP-Link's official channels for firmware updates addressing this issue. As a temporary measure, rebooting the device after suspected exploitation can restore service, but it does not prevent recurrence. Organizations should consider replacing affected devices with models that have received security updates or have better security track records. Implementing network-level intrusion detection systems (IDS) that can identify buffer overflow attack patterns may also help in early detection.
Description
In TP-Link TL-WDR7660 1.0, the rtRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabilities.