Skip to main content
VulnerabilityPublished

CVE-2024-44808: Vypor Attack API System · Improper Input Validation

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 16:39 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 58% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2024

  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 implement network-level access controls to restrict external access to the Vypor Attack API System, such as firewall rules limiting access to trusted IP addresses.
  2. Deploy Web Application Firewalls (WAFs) with custom rules to detect and block malicious payloads targeting the 'user' GET parameter.
  3. Monitor API logs and network traffic for unusual or suspicious requests, especially those containing unexpected input in the 'user' parameter.
  4. Isolate the vulnerable API system from critical internal networks to limit potential lateral movement.
  5. Engage with the vendor or development team to obtain patches or updates as soon as they become available.
  6. Conduct a thorough security review of input validation and sanitization mechanisms in the API codebase to prevent similar vulnerabilities.
  7. Prepare incident response plans to quickly contain and remediate any exploitation attempts.
  8. Consider temporary disabling or replacing the vulnerable API functionality if feasible until a patch is released.

Description

An issue in Vypor Attack API System v.1.0 allows a remote attacker to execute arbitrary code via the user GET parameter.

References

Community reviews

Loading reviews…