CVE-2024-33789: Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 09:15 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 3 May 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
Given the absence of an official patch, organizations should immediately implement compensating controls. These include isolating the affected router from untrusted networks, disabling remote management interfaces if enabled, and restricting access to the /API/info endpoint via firewall rules or network segmentation. Monitoring network traffic for unusual requests targeting the ipurl parameter can help detect exploitation attempts. Users should regularly check for firmware updates from Linksys and apply them promptly once available. Additionally, replacing vulnerable devices with models that have a strong security track record may be warranted for high-risk environments. Employing network intrusion detection systems (NIDS) with signatures for command injection attempts and conducting regular security assessments of network devices will further reduce risk exposure.
Description
Linksys E5600 v1.1.0.26 was discovered to contain a command injection vulnerability via the ipurl parameter at /API/info form endpoint.