CVE-2024-47823

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.

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'],
        );
    }
}

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2024-47823 has a CVSS score of 7.5 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.2, 2.12.7); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2024-47823? CVE-2024-47823 is a high-severity improper input validation vulnerability in livewire/livewire (composer), affecting versions >= 3.0.0-beta.1, < 3.5.2. It is fixed in 3.5.2, 2.12.7. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
2. How severe is CVE-2024-47823? CVE-2024-47823 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of livewire/livewire are affected by CVE-2024-47823? livewire/livewire (composer) versions >= 3.0.0-beta.1, < 3.5.2 is affected.
4. Is there a fix for CVE-2024-47823? Yes. CVE-2024-47823 is fixed in 3.5.2, 2.12.7. Upgrade to this version or later.
5. Is CVE-2024-47823 exploitable, and should I be worried? Whether CVE-2024-47823 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-47823 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-47823?
   • Upgrade livewire/livewire to 3.5.2 or later
   • Upgrade livewire/livewire to 2.12.7 or later