CVE-2025-8522: givanz Vvvebjs · Path Traversal
Affects givanz VvvebjsSource CVE Database V5
Public exploit available · CVSS 2.3 Low.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 4 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| givanz Vvvebjs | Affected
| Fixed in– |
AI-suggested
To mitigate this vulnerability effectively, European organizations should: 1) Immediately audit their use of givanz Vvvebjs and identify any instances running affected versions (2.0.0 through 2.0.4). 3) Implement strict input validation and sanitization on the 'File' parameter within /save.php or equivalent endpoints to prevent directory traversal sequences (e.g., '../'). 4) Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting this endpoint. 5) Restrict file system permissions for the application process to the minimum necessary, preventing access to sensitive directories and files outside the intended scope. 6) Monitor logs for suspicious access patterns or attempts to exploit path traversal, focusing on requests to /save.php with unusual file path parameters. 7) Isolate the application environment using containerization or sandboxing to limit the impact of potential exploitation. 8) Conduct regular security assessments and penetration tests focusing on input validation weaknesses. These steps go beyond generic advice by emphasizing specific controls around the vulnerable endpoint and proactive detection measures.
Description
A vulnerability, which was classified as critical, was found in givanz Vvvebjs up to 2.0.4. Affected is an unknown function of the file /save.php of the component node.js. The manipulation of the argument File leads to path traversal. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used.