Skip to main content
VulnerabilityPublished Updated

CVE-2024-39785: Wavlink AC3000 · Injection

Affects Wavlink AC3000Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
6.3% chance of exploitation in 30 days – higher than 93% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

  1. Immediately audit all Wavlink AC3000 devices in your environment to identify affected firmware versions (M33A8.V5030.210505).
  2. Enforce strong, unique administrative passwords to prevent unauthorized authentication.
  3. Restrict management interface access to trusted IP addresses or via VPN to reduce exposure to authenticated attackers.
  4. Implement network segmentation to isolate vulnerable devices from critical network segments.
  5. Monitor network traffic and device logs for unusual HTTP POST requests to nas.cgi or other suspicious activity indicative of exploitation attempts.
  6. Disable remote management interfaces if not strictly necessary.
  7. Engage with Wavlink or authorized vendors to obtain and apply firmware updates or patches as soon as they become available.
  8. Consider deploying intrusion detection/prevention systems (IDS/IPS) with signatures targeting command injection attempts on nas.cgi endpoints.
  9. Educate network administrators about the risks of command injection vulnerabilities and the importance of timely patching and access control.
  10. Maintain an inventory of all network devices and their firmware versions to facilitate rapid response to emerging threats.

Description

Multiple command execution vulnerabilities exist in the nas.cgi add_dir() functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted HTTP request can lead to arbitrary command execution. An attacker can make an authenticated HTTP request to trigger these vulnerabilities.A command injection vulnerability exists in the adddir_name POST parameter.

References

Community reviews

Loading reviews…