CVE-2024-32305: Tenda A18 · Stack-based Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 16:39 UTC
- EPSS
- 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 17 Apr 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
- Immediately restrict access to the router’s management interfaces by implementing network segmentation and firewall rules to limit exposure to trusted networks only.
- Disable remote management features if not required, especially WAN-side access to the router’s configuration interface.
- Monitor network traffic for unusual patterns or signs of exploitation attempts targeting the PPW parameter or related services.
- Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics capable of detecting stack overflow attempts or anomalous packets targeting Tenda routers.
- Regularly back up router configurations and maintain an incident response plan to quickly restore services if compromise occurs.
- Stay alert for official firmware updates or security advisories from Tenda and apply patches promptly once available.
- Consider replacing vulnerable devices with models from vendors with a stronger security track record if patching is delayed or unavailable.
Description
Tenda A18 v15.03.05.05 firmware has a stack overflow vulnerability located via the PPW parameter in the fromWizardHandle function.