CVE-2024-25182
File Upload Vulnerability in givanz VvvebJs 1.7.2 save.php
Publication date: 2025-12-29
Last updated on: 2025-12-29
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| givanz | vvebjs | 1.7.2 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
givanz VvvebJs 1.7.2 has a File Upload vulnerability via the save.php file, which means that the application improperly handles file uploads, potentially allowing attackers to upload malicious files.
How can this vulnerability impact me? :
This vulnerability can allow attackers to upload malicious files to the server, which may lead to unauthorized code execution, data compromise, or server takeover.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking if the save.php endpoint allows uploading of executable files without proper validation. One way is to attempt a controlled POST request to http://ip:port/save.php with a PHP file payload and then verify if the file is accessible and executable. For example, using curl to upload a test PHP file: curl -F '[email protected]' http://ip:port/save.php and then accessing http://ip:port/test.php?cmd=id to see if command execution is possible. Monitoring HTTP POST requests to save.php for suspicious file uploads and scanning the server for unexpected PHP files in upload directories can also help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting file uploads to the save.php endpoint, implementing strict validation on uploaded files to prevent executable files like PHP scripts, and applying access controls to uploaded files to prevent execution. Additionally, updating or patching the VvvebJs application to a version beyond 1.7.4 (if available) or applying vendor-provided patches is recommended. Monitoring and blocking suspicious POST requests to save.php can also reduce risk. [1]