CVE-2024-25181VulnerabilityPublished 29 Dec 2025Updated 30 Dec 2025

CVE-2024-25181: VvvebJs · n/a

Affects VvvebJsSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.1Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 21% 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:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
GitHubgivanz/VvvebJs`pkg:github/givanz/VvvebJs`Other threats	Affected =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

To mitigate CVE-2024-25181, European organizations should take the following specific actions: 1) Immediately audit all web applications and development environments to identify usage of givanz VvvebJs version 1.7.2 or affected components. 2) If possible, upgrade to a patched or newer version of VvvebJs once available. 3) In the interim, modify the save.php script to implement strict input validation and sanitization on all user-supplied URLs, ensuring only allowed domains or local file paths are processed. 4) Disable PHP's allow_url_fopen directive to prevent file_get_contents from accessing remote URLs, or replace file_get_contents with safer alternatives that do not allow remote requests. 5) Implement web application firewalls (WAFs) with rules to detect and block SSRF patterns and suspicious file access attempts. 6) Conduct thorough logging and monitoring of web server requests to detect anomalous activity indicative of exploitation attempts. 7) Educate developers and administrators about SSRF risks and secure coding practices to prevent similar vulnerabilities. 8) Review network segmentation and access controls to limit the impact of potential SSRF exploitation. These measures go beyond generic advice by focusing on immediate code-level fixes, configuration hardening, and proactive detection tailored to the vulnerability's nature.

Description

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.

Impact

For European organizations, the impact of CVE-2024-25181 can be severe. Exploitation can lead to unauthorized disclosure of sensitive information, including internal network details, credentials, and proprietary data, undermining confidentiality. Integrity can be compromised if attackers leverage the information gained to conduct further attacks such as privilege escalation or code injection. The SSRF aspect can be used to pivot into internal networks, bypassing firewalls and accessing otherwise protected resources, which is particularly concerning for organizations with segmented network architectures. This could lead to data breaches, intellectual property theft, and disruption of business operations. Given the criticality and ease of exploitation, organizations using VvvebJs 1.7.2 in their web applications or development environments face a high risk of compromise. The absence of known exploits in the wild does not reduce the threat, as public disclosure often leads to rapid development of exploit code. Regulatory compliance frameworks in Europe, such as GDPR, impose strict requirements on protecting personal data, and exploitation of this vulnerability could result in significant legal and financial penalties.

CWE-918Server-Side Request Forgery (SSRF) (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

gist.github.com/joaoviictorti/69cbae23d98fb9a1a4b3eee0c305c7de (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Dec 2025, 22:36 UTC

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats