Livewire Remote Code Execution on File Uploads

Exploitation

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

CVSS 4.0

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

EPSS

• CVE-2024-47823: 0.85% estimated exploitation activity in the next 30 days; percentile 58.11 (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.

In livewire/livewire prior to v2.12.7 and v3.5.2, the file extension of an uploaded file is guessed based on the MIME type. As a result, the actual file extension from the file name is not validated. An attacker can therefore bypass the validation by uploading a file with a valid MIME type (e.g., image/png) and a “.php” file extension. If the following criteria are met, the attacker can carry out an RCE attack: - Filename is composed of the original file name using $file-getClientOriginalName() - Files stored directly on your server in a public storage disk - Webserver is configured to execute “.php” files PoC In the following scenario, an attacker could upload a file called shell.php with an image/png MIME type and execute it on the remote server.

Published by the source

8 Oct 2024, 22:19 UTC

Last modified by the source

9 Oct 2024, 23:52 UTC

Source last checked

26 Oct 2026, 14:26 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f3cx-396f-7jqp

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

# Patch Next advisory brief: CVE-2024-47823

Advisory: Livewire Remote Code Execution on File Uploads
IDs: CVE-2024-47823, GHSA-f3cx-396f-7jqp
Record: https://patchnext.com/advisories/cve-2024-47823 (revision 1, source checked 26 Oct 2026, 14:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: livewire/livewire 3.5.2, 2.12.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist livewire/livewire: affected >= 3.0.0-beta.1, < 3.5.2; < 2.12.7; fixed in 3.5.2, 2.12.7

## Suggested inspection (read-only)
- Packagist livewire/livewire: check the installed version with your package manager.

## 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 livewire/livewire.
- 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://github.com/advisories/GHSA-f3cx-396f-7jqp (GitHub-reviewed advisory GHSA-f3cx-396f-7jqp lists affected ranges: Packagist livewire/livewire >=3.0.0-beta.1 =0 <2.12.7)

Commands are suggestions: review each one before running it.