dbcve.org
VvvebjsApplication · Vvveb

CVE-2024-25181

CRITICAL · 9.1 CVSS v3.1 Published 2025-12-29
Fix available
A fix is available. Upgrade to after 1.7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A critical vulnerability has been identified in givanz VvvebJs 1.7.2, which allows both Server-Side Request Forgery (SSRF) and arbitrary file reading. The vulnerability stems from improper handling of user-supplied URLs in the "file_get_contents" function within the "save.php" file.

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 · high confidence

VvvebJs 1.7.2 contains a critical SSRF and arbitrary file reading vulnerability in save.php. User-supplied URLs are directly passed to the PHP file_get_contents() function without proper validation, allowing attackers to make the server fetch arbitrary URLs or read local files from the filesystem.

MitigationApply input validation and allowlist filtering on URL parameters before passing to file_get_contents. Consider using a whitelist of permitted domains/schemes or implementing a sandboxed fetch mechanism. Update to a patched version if available.

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.4

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
None

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

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. Confirm VvvebJs installation and version
    Locate the VvvebJs installation directory and check for a version file or header that displays the software version. Common locations include the main index.php or a version.php file.
    Affected if The installed version is 1.7.4 or lower, as versions up to and including 1.7.4 contain the vulnerability.
  2. Verify save.php exists in the application
    Locate the save.php file within the VvvebJs installation, typically found in the root or admin directory. Check if this file is present on the server.
    Affected if The save.php file exists, as this is the file containing the vulnerable code that uses file_get_contents().
  3. Inspect save.php for vulnerable file_get_contents() usage
    Open save.php and search for usages of file_get_contents() where user-supplied input (such as URL parameters) is passed directly without sanitization or allowlist validation.
    Affected if The code passes URL parameters directly to file_get_contents() without validating the protocol or hostname against an allowlist.
  4. Determine if the vulnerable endpoint is exposed
    Check whether the save.php endpoint is accessible without authentication or with weak authentication. Attempt to access the endpoint or review access control configurations.
    Affected if The save.php endpoint is accessible to unauthenticated users or unauthorized attackers, allowing them to supply arbitrary URLs to the server.

A server is affected if it runs VvvebJs version 1.7.4 or lower with the save.php file present and accessible, containing code that passes user-supplied URLs directly to file_get_contents().

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.

dbcve · scoped
Upgrade available Upgrade to a release after 1.7.4
Interim mitigation

Apply input validation and allowlist filtering on URL parameters before passing to file_get_contents. Consider using a whitelist of permitted domains/schemes or implementing a sandboxed fetch mechanism. Update to a patched version if available.

Recommended fix Moderate confidence

latest stable release (version > 1.7.4)

  1. 1. Backup your current VvvebJs installation and database before making any changes.
  2. 2. Download the latest version of VvvebJs from the official repository (github.com/givanz/Vvvebjs).
  3. 3. Replace the existing installation files with the new version, preserving your configuration and data files.
  4. 4. Verify that the save.php file has been updated with proper URL validation and sanitization.
  5. 5. Test the file saving functionality to ensure legitimate operations still work.
  6. 6. Review server logs for any signs of exploitation attempts.
Caveat review changelog for any breaking changes between your current version and the new release

Generated from the published advisory — verify against the referenced sources before acting.

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 the upgrade done

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-25181 — 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-25181 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