CVE-2024-42640VulnerabilityPublished 11 Oct 2024Updated 15 Oct 2024

CVE-2024-42640: angular-base64-upload · n/a

Affects angular-base64-uploadSource CVE Database V5

Not known to be exploited · public exploit available (Exploit-DB) · 40% EPSS · CVSS 9.8 Critical : upgrade to 0.1.21 as a priority.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

9.8Critical

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

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:H

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

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: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation 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.
2 Exploit-DB entries, the first 175 days after disclosure
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

CVE ID reserved
by mitre
2024-08-05, 67 days before disclosure
CVE published
on cve.org
2024-10-11, t = 0
First Exploit-DB entry (opens in a new tab)
Angular-Base64-Upload Library 0.1.20 - Remote Code Execution (RCE) +1 more
2025-04-04, 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 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

Upgrade adonespitogo/angular-base64-upload to 0.1.21.

Affected software

Product	Affected	Fixed in
GitHubadonespitogo/angular-base64-upload`pkg:github/adonespitogo/angular-base64-upload`Other threats	Affected <0.1.21	Fixed in 0.1.21

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.

Impact

The impact of CVE-2024-42640 is severe for organizations still using vulnerable versions of angular-base64-upload, especially in legacy or unmaintained applications. Successful exploitation results in remote code execution, allowing attackers to execute arbitrary commands on the affected server. This can lead to complete system compromise, data theft, deployment of malware or ransomware, and lateral movement within the network. The vulnerability affects confidentiality, integrity, and availability, potentially causing data breaches, service outages, and reputational damage. Since no authentication or user interaction is required, attackers can exploit this remotely and at scale, increasing the risk of automated attacks. Organizations relying on outdated or unsupported software components are particularly at risk, as they may lack timely patches or mitigations. The absence of known exploits in the wild currently reduces immediate risk, but the critical severity and ease of exploitation mean attackers may develop exploits rapidly. This vulnerability underscores the dangers of using unsupported software and the importance of maintaining updated dependencies.

Summary

CVE-2024-42640 is a critical security vulnerability identified in angular-base64-upload, a library used for handling base64 file uploads in AngularJS applications. Versions prior to 0.1.21 contain a severe flaw in the demo/server.php script, which does not enforce any authentication or validation on uploaded files. This allows an unauthenticated attacker to upload arbitrary files, including malicious scripts, to the server. Once uploaded, these files are accessible through the demo/uploads directory and can be executed by the server, leading to remote code execution (RCE). The vulnerability is categorized under CWE-434, indicating an unrestricted file upload issue where dangerous file types can be uploaded without proper filtering or sanitization. The CVSS 3.1 base score is 9.8, reflecting the vulnerability’s ease of exploitation over the network without any privileges or user interaction, and its full impact on confidentiality, integrity, and availability of the affected system. Exploitation could allow attackers to take full control of the server, execute arbitrary commands, and potentially pivot to other parts of the network. No known exploits have been publicly reported yet, but the high severity and straightforward exploitation vector make it a significant threat.

Exploit-DB

Nuclei detection templates

Angular-Base64-Upload - Remote Code Executioncritical (opens in a new tab)

Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.

CWE-434Unrestricted Upload of File with Dangerous Type (opens in a new tab)
Base weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #12OWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
Architecture and Design
Generate a new, unique filename for an uploaded file instead of using the user-supplied filename, so that no external input is used at all.
Architecture and Design · Enforcement by Conversion
When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
Architecture and Design
Consider storing the uploaded files outside of the web document root entirely. Then, use other mechanisms to deliver the files dynamically.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Web Service Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
File Upload (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V12.5.2 (opens in a new tab)
V13.1.5 (opens in a new tab)
V12.2.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 06:08 UTC

Public exploits and detection2 Exploit-DB entries, a Nuclei detection template

WeaknessesCWE-434

Technical details

References

Community reviews

Related threats