CVE-2024-48710: 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 31% 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 CVE-2024-48710, organizations should first restrict network access to the TP-Link TL-WDR7660 management interfaces, limiting exposure to trusted networks and devices only. Implement network segmentation to isolate vulnerable routers from untrusted or guest networks. Monitor network traffic for unusual or malformed packets targeting router configuration functions. Since no official patches are currently available, consider temporary mitigation by disabling remote management features if possible. Engage with TP-Link support channels to obtain information on upcoming firmware updates addressing this vulnerability. Maintain an inventory of affected devices and plan for timely firmware upgrades once patches are released. Additionally, implement network-level protections such as intrusion detection/prevention systems (IDS/IPS) that can detect anomalous traffic patterns indicative of exploitation attempts. Regularly audit router configurations and logs for signs of exploitation or instability.
Description
In TP-Link TL-WDR7660 1.0, the wlanTimerRuleJsonToBin function handles the parameter string name without checking it, which can lead to stack overflow vulnerabilities.