CVE-2024-42640: angular-base64-upload · Unrestricted File Upload
Affects angular-base64-uploadSource CVE Database V5
Public exploit available (Exploit-DB) · 40% EPSS · CVSS 9.8 Critical : upgrade to 0.1.21 as a priority.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 40.2% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.1.21
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 11 Oct 2024
Detectable: evidence found.
nuclei template: Angular-Base64-Upload - Remote Code Execution
Weaponised: evidence found.
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
Timeline
CVE ID reserved
by MITRE Corporation
, 67 days before disclosure
CVE published
on cve.org
, t = 0
First Exploit-DB entry (opens in a new tab)
Angular-Base64-Upload Library 0.1.20 - Remote Code Execution (RCE) +1 more
, 175 days after disclosure
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 26 Oct 2026.
What to do
Upgrade adonespitogo/angular-base64-upload to 0.1.21.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubadonespitogo/angular-base64-uploadpkg:github/adonespitogo/angular-base64-uploadOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Given that the affected angular-base64-upload versions are no longer supported and no official patches exist, organizations should take immediate steps to mitigate risk. First, remove or disable the vulnerable demo/server.php component entirely, especially if it is exposed to untrusted networks. Restrict access to the demo/uploads directory via web server configuration to prevent execution of uploaded files. Implement strict input validation and file type restrictions on any file upload functionality, replacing or upgrading to a maintained and secure alternative library if possible. Employ network-level protections such as web application firewalls (WAFs) to detect and block suspicious upload attempts targeting this vulnerability. Conduct thorough audits of legacy applications to identify any usage of angular-base64-upload and plan for migration to supported solutions. Monitor logs for unusual file uploads or execution attempts related to demo/uploads. Finally, educate development teams on the risks of using unsupported third-party components and enforce policies for regular dependency updates and vulnerability management.
Description
angular-base64-upload prior to v0.1.21 is vulnerable to unauthenticated remote code execution via demo/server.php. Exploiting this vulnerability allows an attacker to upload arbitrary content to the server, which can subsequently be accessed through demo/uploads. This leads to the execution of previously uploaded content and enables the attacker to achieve code execution on the server. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.