CVE-2024-47823: Livewire Remote Code Execution (RCE) on File Uploads

Published Oct 8, 2024
·
Updated

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. php class SomeComponent extends Component { use WithFileUploads;

#[Validate('image|extensions:png')] public $file;

public function save() { $this->validate();

$this->file->storeAs( path: 'images', name: $this->file->getClientOriginalName(), options: ['disk' => 'public'], ); } }

Other sources

Livewire is a full-stack framework for Laravel that allows for dynamic UI components without leaving PHP. In livewire/livewire prior to 2.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: 1. Filename is composed of the original file name using $file->getClientOriginalName(). 2. Files stored directly on your server in a public storage disk. 3. Webserver is configured to execute “.php” files. This issue has been addressed in release versions 2.12.7 and 3.5.2. All users are advised to upgrade. There are no known workarounds for this vulnerability.

NVD

Affected Software

4 affected componentsFixes available
composer/livewire/livewire<2.12.7
2.12.7
composer/livewire/livewire>=3.0.0-beta.1<3.5.2
3.5.2
Laravel Livewire<2.12.7
Laravel Livewire>=3.0.0<3.5.2

Event History

Oct 8, 2024
CVE Published
via MITRE·05:48 PM
Data Sourced
via MITRE·05:48 PM
DescriptionWeakness
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 PM
RemedyAffected Software
Advisory Published
via GitHub·10:19 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-47823?

CVE-2024-47823 is considered a moderate severity vulnerability due to the potential for file upload attacks.

2

How do I fix CVE-2024-47823?

To fix CVE-2024-47823, update livewire/livewire to version 2.12.7 or 3.5.2 or later.

3

Who is affected by CVE-2024-47823?

CVE-2024-47823 affects users of livewire/livewire versions prior to 2.12.7 and between 3.0.0-beta.1 and 3.5.2.

4

What type of vulnerability is CVE-2024-47823?

CVE-2024-47823 is a file upload vulnerability that allows attackers to bypass file extension validation.

5

Can exploiting CVE-2024-47823 lead to further security issues?

Yes, exploiting CVE-2024-47823 could potentially lead to arbitrary code execution or other attacks if malicious files are uploaded.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203