Skip to main content
CVE-2024-25182VulnerabilityPublished Updated

CVE-2024-25182: vvvebjs · n/a

Affects vvvebjsSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 08:30 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 instances of the vulnerable save.php endpoint. 2. Implement strict server-side validation to restrict file uploads by type, size, and content, allowing only safe file formats. 3. Disable direct execution permissions on upload directories to prevent execution of uploaded malicious files. 4. Employ web application firewalls (WAFs) with rules to detect and block suspicious file upload attempts targeting save.php. 5. Monitor logs for unusual upload activity or access patterns to detect exploitation attempts early. 6. Isolate affected web servers in segmented network zones to limit lateral movement if compromised. 7. Stay alert for official patches or updates from VvvebJs maintainers and apply them promptly once released. 8. Educate development teams on secure file upload practices and the risks of CWE-434 vulnerabilities. 9. Consider temporary disabling or restricting the save.php functionality if feasible until a patch is available.

Description

givanz VvvebJs 1.7.2 suffers from a File Upload vulnerability via save.php.

References

Community reviews

Loading reviews…