dbcve.org
VvvebjsApplication · Vvveb

CVE-2024-25182

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

VvvebJs 1.7.2 contains a file upload vulnerability in the save.php endpoint that allows attackers to upload malicious files, likely leading to remote code execution given the critical CVSS score.

MitigationImplement strict file type validation, restrict uploaded file extensions, sanitize filenames, and store uploads outside the web root or with non-executable permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
VvvebjsApplication
Affected:= 1.7.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify VvvebJs version
    Locate the version file or check the main JavaScript/library files for the version identifier. Common paths include version.js, package.json in the installation directory, or the main vvveb.js file.
    Affected if The installed version is exactly 1.7.2
  2. Verify save.php exists
    Check for the presence of the file save.php in the web application's directory structure, typically found in the admin or root folder of the VvvebJs installation.
    Affected if save.php exists in the accessible web directory
  3. Confirm save.php is reachable without authentication
    Attempt to access the save.php endpoint directly via HTTP/HTTPS request without providing any authentication credentials.
    Affected if The save.php endpoint responds without requiring login or session authentication
  4. Test if file upload parameter is accepted
    Send a POST request to save.php with a simple test file (such as a text file) to see if the endpoint accepts and processes file uploads without validation.
    Affected if The endpoint accepts and processes file uploads without requiring authentication or validation

If VvvebJs version 1.7.2 is running and the save.php endpoint is accessible without authentication, the system is vulnerable to unauthenticated arbitrary file upload.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict file type validation, restrict uploaded file extensions, sanitize filenames, and store uploads outside the web root or with non-executable permissions.

Fix this in Vvvebjs Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25182 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data