On this page
Livewire v3 up to and including 3.6.3 has an unauthenticated remote command execution flaw, CVE-2025-54068. It was fixed in 3.6.4 and has been on CISA's exploited list since 20 March 2026. Read the version in the deployed composer.lock or with composer show livewire/livewire. If it is 3.6.3 or lower, upgrade to the latest 3.8 or 4.4 release, redeploy and restart the workers.
| Fact | Detail | Source |
|---|---|---|
| CVE | CVE-2025-54068, CWE-94 (code injection), in livewire/livewire | NVD |
| Severity | CVSS v4 9.2 (GitHub), CVSS v3.1 9.8 (NVD) | GitHub advisory database |
| Affected | Livewire v3, from 3.0.0-beta.1 up to and including 3.6.3 | Livewire advisory |
| Fixed | 3.6.4, released 17 July 2025 | Release notes |
| Workaround | None known. The advisory says to upgrade | Livewire advisory |
| Exploitation | In CISA KEV: added 20 March 2026, federal due date 3 April 2026, ransomware use flag "unknown" | CISA catalog |
| Checked | 4 November 2026 | this page |
Which Livewire versions are affected?
Only Livewire 3 releases from 3.0.0-beta.1 through 3.6.3 are affected by this CVE. The advisory describes it as a flaw that lets an unauthenticated attacker run commands "in specific scenarios", arising during property update hydration. It needs no login and no user action. The maintainers did not publish details at disclosure, and we do not reproduce any.
The version you move to matters, because Livewire shipped other fixes after 3.6.4. This table is what the Livewire advisories and Packagist showed on 4 November 2026.
| Your version | CVE-2025-54068 | Also relevant | Move to |
|---|---|---|---|
| 2.x | Not listed | 2.12.6 and below: CVE-2024-47823, file upload RCE, fixed in 2.12.7 | 2.12.7 at least, then plan the move to 3 or 4 |
| 3.0.0-beta.1 to 3.6.3 | Affected | Also below 3.5.2 for CVE-2024-47823 | Latest 3.8 (3.8.11, 21 October 2026) or 4.4.8 |
| 3.6.4 to 3.8.2 | Fixed | CVE-2026-81887, DOM-based XSS, medium (CVSS v4 5.1), published 10 August 2026 | 3.8.3 or later |
| 3.8.3 and later | Fixed | None listed in the advisories at our check | Stay on the latest 3.8 |
| 4.0.0-beta.1 to 4.3.3 | Not listed | The same XSS, fixed in 4.3.4 | 4.4.8 |
| 4.3.0 to 4.4.7 | Not listed | An authorization bypass in #[Authorize], medium, published 22 October 2026, fixed in 4.4.8 | 4.4.8 |
One detail trips people up. The advisory text says "up to and including v3.6.3", and the fixed version is 3.6.4. If you are on exactly 3.6.3, you are affected. The older 2024 file-upload flaw is a separate bug with its own fix, CVE-2024-47823, and a site can have both.
How do I find the Livewire version actually running?
Read it on the server that serves the site, from the deployed project folder. Three places can disagree, and only one counts.
composer.jsonholds a range such as^3.0. It says what is allowed, not what is installed.composer.lockholds the exact version. Composer's documentation says that when a lock file exists, install uses the exact versions listed in it, and that update rewrites the lock file. A project can allow 3.8 and still run 3.5 if nobody ran an update.- The deployed folder is what runs. On a host, a container or a release directory it can differ from the repository.
On the server, in the project root:
composer show livewire/livewire
composer audit
composer show prints the installed version. composer audit checks installed packages against security advisories from the Packagist API by default and, per the Composer docs, exits with code 1 when it finds matches. It reads installed packages, so run it where they are installed.
If you cannot reach the server, the same facts are in the deployed composer.lock. Ask whoever deploys the site. If Livewire arrives through another package, composer why livewire/livewire shows which one requires it.
Can you see the Livewire version from outside?
Not reliably. Livewire 3 documents that it serves its JavaScript at /livewire/livewire.js, with no version in the URL. That makes "this site uses Livewire" visible from outside and "this site runs 3.6.3" usually not.
A lookup from outside can match a version only when the version is exposed. When it is not, the honest result is unknown, and the answer has to come from the lock file. See why a version can stay hidden from outside scans.
How do I upgrade?
On staging first, then production. The aim is to reach 3.8.11 or later in 3.x, or 4.4.8 in 4.x, and to prove the running site picked it up.
- Back up the code and the database, and commit the current
composer.lock. - Update only Livewire and what it needs:
composer update livewire/livewire --with-dependencies. - Read the result with
composer show livewire/livewireand confirm it is at least 3.8.3, ideally 3.8.11. - Run your test suite and click through pages that use Livewire components, including forms and file uploads.
- Commit the new
composer.lockand deploy from it. - Restart PHP-FPM or your web server, and restart queue workers and any other long-running PHP process.
- Run
composer auditon the server after the deploy.
Version 3.8.11 requires PHP ^8.1 and supports Laravel 10 to 13, according to Packagist at our check. If you want Livewire 4, the upgrade guide lists its high-impact changes first and starts with composer require livewire/livewire:^4.0. A move across a major version is a project of its own. If you cannot do it this week, take the 3.8 line now and plan 4 later. A Laravel site also depends on its PHP runtime, which is a separate patch covered in the Laravel and CMS PHP2Shell checklist, and the other framework guides cover Next.js, Django and more.
If an agency, host or freelancer deploys your site
Send this and keep the reply:
For [your domain], which version of
livewire/livewireis in thecomposer.lockthat is deployed in production right now? When was it deployed, and were PHP-FPM and all queue workers restarted after that? If it is 3.6.3 or lower, when will it move to 3.8.3 or later, and has anyone checked the server for changes since 17 July 2025?
"We updated everything" is not an answer. A version number, a deploy time and a restart time are.
Was this exploited, and what should I look for?
CISA's catalog lists it as Laravel Livewire Code Injection Vulnerability, added 20 March 2026. CISA's own criteria for adding an entry include reliable evidence of active exploitation in the wild. Federal civilian agencies must remediate on a deadline, and CISA strongly recommends that all stakeholders treat catalog entries as items to address immediately. The entry gives no start date and no victims, and we name none.
A third-party report from ThreatHunter, published 14 March 2026 and listed by NVD, describes one actor using a scanning template for this CVE and confirming nine vulnerable targets. That is vendor-claimed and we have not verified it.
The fix shipped on 17 July 2025, so the window for an unpatched site is long. Upgrading closes the hole and removes nothing planted earlier. If you were on 3.6.3 or lower while reachable, check:
- unexpected PHP files in
public,storageand upload folders - scheduled tasks, cron entries and queue jobs you did not create
- new or changed users, especially administrators
- a modified
.env, and outbound connections from the web server that you cannot explain
If you find anything, treat the server as compromised and follow the step-by-step response for a compromised site, then rotate the secrets the application could read, including APP_KEY, database passwords and API keys. If you find nothing, that is an absence of signs and not proof, because logs often have gaps. Keep patch state and compromise evidence as two separate answers. If APP_KEY was readable, how to rotate a leaked Laravel key safely is its own job, and checking whether your .env is publicly readable shows if the file was also reachable from outside.
Am I affected? A three-state self-test
Am I affected? Where you stand right now
A check from outside can sometimes see that a site uses Livewire. It cannot read your lock file, your deployed folder or the time your workers last started.
- Detected The site shows a Livewire v3 version at or below 3.6.3, or your own lock file does. Treat it as exposed. Upgrade today, restart the workers, then run the look-back above for activity since 17 July 2025.
- Unknown You use Livewire but cannot see the version, or you do not know which copy is deployed. This is the common case. Get the installed version from the server or from whoever deploys, using the question above.
- Confirmed by owner evidence
composer show livewire/livewireon the production server reports 3.8.3 or later (or 4.4.8), and PHP and queue workers started after that deploy. This CVE is closed on that server. Whether anything got in before the upgrade is a separate question.
No scan, ours included, moves you from "unknown" to "confirmed".
What does Red check?
The free scan reads the stack your site serves and matches each version to known vulnerabilities. One per domain, no card. It is a lookup: it can say a version is affected, not whether your setup is exposed. When Livewire's version is not visible from outside, the scan cannot match it, which is why the server-side check above comes first. It also looks at things around an application like this one, such as .env and .git exposure, and panels or debug pages left online.
You sign in with Google or GitHub, or an emailed six-digit code, and add one DNS TXT record to prove the domain is yours. The full scan is $100 per scan and sends an AI red team to find what is reachable from outside. Fixing is yours or your host's. For how to prove a fix landed, see proving the patch actually landed. More active issues are in the October 2026 tracker.
Questions people ask
How do I check which Livewire version my site is running?
Run composer show livewire/livewire in the project folder on the server that serves the site, or open composer.lock and read the version next to livewire/livewire. The version in composer.json is only a range. Make sure you look at the deployed copy, not a laptop copy.
Is Livewire 3.6.4 enough, or should I go further?
3.6.4 fixes this one flaw. Livewire has since published a DOM-based XSS fix in 3.8.3 and 4.3.4, so go to the latest 3.8 release or to 4.4.8 if you can. At our 4 November 2026 check those were 3.8.11 and 4.4.8.
Does Livewire 2 have this vulnerability?
CVE-2025-54068 is listed for Livewire v3 only, from 3.0.0-beta.1 up to and including 3.6.3. Livewire 2 is not listed for it. Version 2.12.6 and below does have a different, older flaw (CVE-2024-47823), so a v2 site still needs an upgrade plan.
Is CVE-2025-54068 being exploited?
CISA added it to the Known Exploited Vulnerabilities catalog on 20 March 2026, which CISA says requires reliable evidence of active exploitation. The entry gives no start date and flags no known ransomware use. Treat any unpatched site that was reachable as one to check.
I use Cloudflare or another WAF. Do I still need to upgrade?
Yes. Livewire's advisory says there is no known workaround and tells users to upgrade. A proxy rule is at best a stopgap, and it only helps while traffic goes through it. Upgrade the package, redeploy, and restart the workers.
Can I upgrade to 3.8.11 on Laravel 10 and PHP 8.1?
According to Packagist at our check, 3.8.11 requires PHP ^8.1 and supports Laravel 10, 11, 12 and 13. Run the update on staging first, since a jump from an early 3.x release crosses many changes.
Sources
- GHSA-29cq-5w36-x7w3: Livewire remote command execution during property update hydration (livewire/livewire advisory)The vendor advisory. Affected range, patched version 3.6.4, no workaround. Checked 4 November 2026.
- GitHub Advisory Database: GHSA-29cq-5w36-x7w3CVSS v4 9.2 and CVSS v3.1 9.8, CWE-94, vulnerable range from 3.0.0-beta.1 below 3.6.4. Last updated 20 March 2026.
- NVD: CVE-2025-54068Published 17 July 2025, last modified 17 June 2026. Carries the CISA fields. Read through the NVD API on 24 October 2026.
- CISA Known Exploited Vulnerabilities catalog: CVE-2025-54068Laravel Livewire Code Injection Vulnerability. Added 20 March 2026, due 3 April 2026.
- CISA: Known Exploited Vulnerabilities Catalog, criteria and recommendationsWhat a catalog entry means and what CISA recommends to organisations outside the federal government.
- Livewire v3.6.4 release notesThe fixing release, 17 July 2025, entry on property update hydration.
- Patch commit ef04be7 (livewire/livewire)The change referenced by NVD as the patch.
- livewire/livewire security advisoriesAll four published advisories, including the 2026 ones that matter when choosing a target version.
- GHSA-g3hc-697w-wm82: CVE-2026-81887, DOM-based XSS (livewire/livewire advisory)Medium, CVSS v4 5.1. Fixed in 3.8.3 and 4.3.4. Published 10 August 2026.
- GHSA-f3cx-396f-7jqp: CVE-2024-47823, remote code execution on file uploads (livewire/livewire advisory)An older, separate flaw. Fixed in 3.5.2 and 2.12.7. Published 8 October 2024.
- Packagist metadata for livewire/livewireLatest releases: 3.8.11 and 4.4.8, both 21 October 2026. 3.8.11 requires PHP ^8.1 and Laravel 10 to 13. Read 4 November 2026: no newer release.
- Livewire v3 installation docsDocuments that the JavaScript asset is served at /livewire/livewire.js, with no version in the URL.
- Livewire documentation: upgrading from v3 to v4The v4 upgrade steps.
- Composer documentation: basic usageHow composer.lock decides the installed version.
- Composer documentation: command-line interface (show, audit, why, update)
- ThreatHunter report, 14 March 2026 (third-party reference listed by NVD)Vendor-claimed threat intelligence. Not a primary source for the vulnerability itself.
Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.