CVE-2024-29272 json
VvvebJs Arbitrary File Upload vulnerability
published 2y ago modified 4mo ago also GHSA-pmm3-68q9-57jg , EUVD-2024-0980
- cvss
- 6.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 9.4%
- EPSS 9.4% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
Arbitrary File Upload vulnerability in VvvebJs before version 1.7.5, allows unauthenticated remote attackers to execute arbitrary code and obtain sensitive information via the sanitizeFileName parameter in save.php.
Patch / fix
Is CVE-2024-29272 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2y ago
Exploit prediction
9.37% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-11).
Exploits and checks
- github.com https://github.com/givanz/VvvebJs/issues/343 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| CNA | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| GitHub | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | vvvebJs | <1.7.5 |
1.7.5 |
Affected products
- givanz vvvebjs
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
github.com
/givanz/VvvebJs/commit/c6422cfd4d835c2fa6d512645e30015f24538ef0
web, patch
-
github.com
/givanz/VvvebJs/issues/343
web, exploit, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-29272
advisory
-
github.com
/givanz/VvvebJs
package
Sources
- CVE List CVE-2024-29272
- GitHub Advisory GHSA-pmm3-68q9-57jg
- NVD CVE-2024-29272
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.