angular-base64-upload vulnerable to unauthenticated remote code execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-42640: 40.21% estimated exploitation activity in the next 30 days; percentile 98.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

angular-base64-upload versions prior to v0.1.21 are vulnerable to unauthenticated remote code execution via the angular-base64-upload/demo/server.php endpoint. Exploitation of this vulnerability involves uploading arbitrary file content to the server, which can subsequently accessed through the angular-base64-upload/demo/uploads endpoint. This leads to the execution of previously uploaded content which enables the attacker to achieve code execution on the server. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Published by the source

11 Oct 2024, 18:32 UTC

Last modified by the source

11 Oct 2024, 20:12 UTC

Source last checked

26 Oct 2026, 12:31 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-vgxq-6rcf-qwrw

2. Revision 2 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-vgxq-6rcf-qwrw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-42640

Advisory: angular-base64-upload vulnerable to unauthenticated remote code execution
IDs: CVE-2024-42640, GHSA-vgxq-6rcf-qwrw
Record: https://patchnext.com/advisories/cve-2024-42640 (revision 3, source checked 26 Oct 2026, 12:31 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: angular-base64-upload 0.1.21. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm angular-base64-upload: affected < 0.1.21; fixed in 0.1.21

## Suggested inspection (read-only)
- `npm ls angular-base64-upload --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on angular-base64-upload.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-vgxq-6rcf-qwrw (OSV record GHSA-vgxq-6rcf-qwrw lists affected ranges: npm angular-base64-upload >=0 <0.1.21 (fixed))
- Verified: https://github.com/advisories/GHSA-vgxq-6rcf-qwrw (GitHub-reviewed advisory GHSA-vgxq-6rcf-qwrw lists affected ranges: npm angular-base64-upload >=0 <0.1.21)

Commands are suggestions: review each one before running it.