Skip to main content
VulnerabilityPublished Updated

CVE-2024-27480: vvvebjs · Unrestricted File Upload

Affects vvvebjsSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

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

Affected software

ProductAffectedFixed in
npmgivanz/vvvebjspkg:npm/givanz/vvvebjsOther threatsAffected
  • =1.7.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediately audit all web applications using VvvebJs 1.7.2 to identify exposure to the vulnerable file upload functionality.
  2. Disable file upload features in VvvebJs if they are not essential to the application’s operation.
  3. Implement strict server-side validation of uploaded files, including checking file type, size, and content signatures to prevent malicious files.
  4. Employ allow-listing of acceptable file extensions and reject all others.
  5. Use sandboxing or isolated environments to handle file uploads, preventing direct execution on production servers.
  6. Monitor web server logs and network traffic for unusual upload patterns or execution attempts.
  7. Apply web application firewalls (WAFs) with custom rules to detect and block suspicious upload requests.
  8. Prepare incident response plans specifically addressing potential exploitation of file upload vulnerabilities.
  9. Stay alert for official patches or updates from the VvvebJs maintainers and apply them promptly once available.
  10. Educate developers and administrators about secure file handling practices to prevent similar vulnerabilities in the future.

Description

givanz VvvebJs 1.7.2 is vulnerable to Insecure File Upload.

References

Community reviews

Loading reviews…