Laravel Livewire flaw exploited: update to 3.6.4
In March CISA confirmed attacks on CVE-2025-54068 in Laravel Livewire, fixed since July 2025. Why a framework's packages need patching like the framework.
Published · 3 min read

On 20 March 2026, the US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2025-54068, a flaw in Laravel Livewire, to its list of vulnerabilities that attackers are known to be exploiting. Livewire is a package Laravel applications use to build interactive screens in PHP, and in version 3, up to and including 3.6.3, the flaw lets an attacker with no account run commands on the server, where a component is mounted and configured in a particular way. The fix, version 3.6.4, had been out since 17 July 2025, and the maintainers say there is no workaround. The systems at risk in March were the ones nobody had updated for eight months.
The details had been public since 23 December 2025, when Synacktiv, whose researchers found the flaw and reported it in June 2025, published its research. CISA gave US federal agencies until 3 April to fix it. What followed shows the cost of waiting: on 24 May Imperva saw attempts to exploit the flaw, and its report of 23 June describes a campaign that took credentials from 6,167 applications, among them 381 valid AWS keys and 188 live keys for a payment service. A Laravel application keeps its database passwords and service keys in a single .env file, Imperva notes, so one break-in hands over all of them.
A framework is only as patched as its packages
The flaw was in Livewire, not in Laravel itself, so a system could run an up-to-date framework and still be exposed. A Laravel system is the framework plus many packages, each with its own maintainers and its own security fixes, and each held at an exact version in a file called composer.lock. That is what keeps a system stable: every install uses the versions in the lock file until someone deliberately updates them. It is also why a system can seem well kept and still run a package whose fix has been waiting for months.
It is an easy state for a bespoke system to fall into after handover. It works, nobody is paid to touch it, and the lock file keeps it exactly as it was on the day it went live, while the office that owns it may not know which packages it runs.
What it means for the systems I build
Laravel is part of the stack I build with, listed on my track record, so this is my own ground. For any Laravel system, whoever built it, I would want composer audit run on a schedule rather than when someone remembers, security fixes for packages applied within days, the same as for the framework, and a named person who sees the result. Composer's audit checks the installed packages against published security advisories, and it flags abandoned packages too, which matters as much: a package nobody maintains will never get its fix.
Five checks for a Laravel system
- Find livewire/livewire in composer.lock. If it is a version 3 release below 3.6.4, update it; there is no workaround.
- Run composer audit with --locked, which reads the versions in the lock file, and fix what it reports, the critical ones first.
- If a vulnerable version was reachable from the internet, treat the server as possibly compromised. Rotate the database passwords and keys in .env, and generate a new APP_KEY, a step Synacktiv calls mandatory after exploitation, because an attacker holding the old key can still compromise the server.
- Watch what the web server connects out to. Imperva saw stolen data leave over FTP, Telegram and GoFile, and recommends blocking outbound FTP and alerting on connections to the other two.
- Ask whoever maintains the system how quickly package security fixes are applied, and who reads the audit results.
If your office owns a Laravel system nobody has updated since it went live, the fit check is a good place to raise it.
Sources
- Cybersecurity and Infrastructure Security Agency, CISA Adds Five Known Exploited Vulnerabilities to Catalog, 20 March 2026
- Livewire, Livewire remote command execution during property update hydration, 17 July 2025
- Synacktiv, Livewire: remote command execution through unmarshaling, 8 January 2026
- Imperva, CVE-2025-54068 Laravel Livewire Credential Theft Campaign: 6,000+ Applications Compromised, 23 June 2026
- ThaiCERT, CISA Adds Apple, Laravel Livewire, and Craft CMS Vulnerabilities to KEV Catalog Following Active Exploitation, 24 March 2026
- Livewire, Quickstart
- Composer, Command-line interface / Commands
- Synacktiv, Livewire: remote command execution through unmarshaling, 23 December 2025
Enrique Lacambra III builds internal business systems from Cainta, Rizal.
Tell me what is broken and I will tell you if it is worth building. A 20-minute call, no charge, and I will say so if you do not need me.
