Skip to main content
Mallory
CriticalExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-54068: Unauthenticated Remote Code Execution in Laravel Livewire v3

Published Jul 17, 2025 · Updated 17 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days3 mentions · peak 2 in a dayToday
CVSS9.2Critical · v4
EPSS96.3%100th percentile
CISA KEVYesAdded Mar 20, 2026
In the wildActivePer CISA KEV
Vendor
Laravel
IdentifiersCVE-2025-54068CWE-94 · Improper Control of Generation of…

CVE-2025-54068 is a code injection vulnerability affecting Laravel Livewire v3 through version 3.6.3. Improper handling of component property updates during recursive hydration allows attackers to introduce synthesizer metadata through the updates mechanism and instantiate PHP objects capable of triggering code-execution gadget chains. Exploitation bypasses the need to know the Laravel application encryption key or forge a signed snapshot. A component must be mounted and configured in an exploitable manner; not every Livewire installation is necessarily exploitable. Authentication and user interaction are not required. Earlier Livewire major versions are unaffected. Livewire 3.6.4 corrects the issue by preserving the original snapshot context during recursive property-update hydration.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits arbitrary PHP code and operating-system command execution with the privileges of the application process, compromising application confidentiality, integrity, and availability. Observed exploitation has supported credential harvesting, database theft, and deployment of botnet malware. Exposed application secrets can enable subsequent access to databases, cloud services, payment systems, and other connected resources, subject to the permissions of the stolen credentials.

Mitigation

If you can’t patch tonight, do this now.

No known workaround eliminates the vulnerability without upgrading. As defense in depth, use web application firewall protections capable of detecting malicious Livewire hydration or deserialization payloads, restrict unnecessary outbound connections, block outbound FTP where not required, and monitor unusual traffic to messaging and file-sharing services. These controls may reduce exploitation or exfiltration risk but do not replace the patch.

Remediation

Patch, then assume compromise.

Upgrade affected Livewire v3 installations to version 3.6.4 or a later supported release. The corrected hydration logic preserves the original raw snapshot context during recursive updates. Investigate potentially compromised deployments for unauthorized code execution, malicious payloads, and secret theft. Where exposure or compromise is established, rotate affected database credentials, API keys, cloud credentials, application encryption keys, and other secrets; patching alone does not invalidate stolen credentials or remove attacker persistence.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 8 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2025-54068Repository purpose: an enhanced Python exploit tool for CVE-2025-54068 targeting Laravel Livewire, enabling remote command execution by sending crafted Livewire component update requests. It is based on Synacktiv's Livepyre concept and adds usability features (auto URL formatting, custom payload generation, and mass scanning). Key components: - gas.py: main CLI entry point. Supports single-target exploitation, payload-only generation, and mass checking. Can switch to a custom payload mode that base64-encodes a locally generated serialized PHP object and sets function=unserialize to execute it remotely. - exploit/exploit.py: shared base class providing URL normalization, session setup (optional proxy/headers), HTML parsing helpers to extract CSRF token and Livewire update URI, snapshot extraction, and version fingerprinting using versions.json. - exploit/exploit_appkey.py: exploit path when APP_KEY is known. Recomputes Livewire snapshot checksum (HMAC-SHA256 using parsed APP_KEY) after injecting a gadget chain into snapshot data, then POSTs to the update endpoint. - exploit/exploit_wappkey.py: exploit path without APP_KEY. Performs a two-stage approach: (1) attempts to coerce a chosen snapshot parameter into an array/object form via an update request, then (2) sends a second request using payload.json with placeholders replaced to trigger the gadget chain and execute the chosen PHP function/parameter. Includes a version check (<3.6.4) with optional --force. - exploit/laravel_crypto/*: Laravel-compatible AES/HMAC helpers used for APP_KEY parsing and checksum/signing logic. - exploit/payload_generator.py: generates serialized PHP payloads locally (via running php) for richer post-exploitation primitives (shell/file read/write/list/phpinfo/config/eval, multi-command). Used by gas.py custom payload mode. - exploit/mass.py: multi-threaded Livewire presence/version/vulnerability checker with optional realtime result saving. Exploit capabilities: - Detects Livewire presence and extracts wire:snapshot values from HTML. - Discovers Livewire update endpoint (relative or absolute) and CSRF token. - Executes arbitrary PHP functions with attacker-controlled parameters (default system('id')). - Optional custom payload mode: delivers attacker-defined serialized PHP object and triggers it via unserialize(), enabling multi-function command execution and file operations. - Mass scanning/checking of multiple targets with threading and output to JSON/CSV. Notable observables: - Network behavior: HEAD/GET to the provided target URL, then POST JSON to the discovered Livewire update URI. - Local artifacts: versions.json and payload.json templates; optional dependency on local 'php' binary for payload generation.haxorstars · Disclosed Jan 20, 2026 · python · php · networkWeaponizedLivepyreThis repository, 'Livepyre', is a Python-based exploit tool targeting CVE-2025-54068, a remote command execution (RCE) vulnerability in Laravel Livewire versions prior to 3.6.4. The tool is structured with a main entry point (Livepyre.py) that orchestrates exploitation using two main strategies: with and without knowledge of the Laravel APP_KEY. The 'exploit' directory contains the core logic, including modules for cryptographic operations compatible with Laravel's encryption scheme, payload construction, and version detection. The exploit works by sending specially crafted HTTP POST requests to Livewire endpoints, abusing the snapshot mechanism to trigger PHP object injection and execute arbitrary system commands. The tool can automatically detect vulnerable versions, enumerate exploitable parameters, and adapt its payloads based on the target's configuration. The repository includes example usage, payload templates, and a comprehensive version hash list for Livewire. No hardcoded IPs or domains are present, but the tool requires the attacker to specify the target URL. The exploit is operational and provides direct RCE if successful.synacktiv · Disclosed Dec 23, 2025 · python · networkOperationalCVE-2025-54068-livewireThis repository provides a minimal, reproducible lab environment for CVE-2025-54068, a critical remote code execution vulnerability in Livewire v3.6.3 (used with Laravel 11.0.0). The structure includes Docker and docker-compose files to build and run the vulnerable application, a sample Livewire component (Counter) intentionally left untyped to facilitate exploitation, and a Python proof-of-concept exploit (scripts/poc.py). The exploit works in two stages: first, it manipulates a Livewire component parameter to trigger a type confusion, then it sends a crafted PHP object injection payload to achieve RCE. The PoC confirms exploitation by echoing a marker string and checking for its presence in the HTTP response. The main endpoints involved are the web interface at http://localhost:18081/ and the Livewire update endpoint discovered dynamically by the exploit script. The repository is well-structured for security researchers to reproduce and validate the vulnerability, with clear separation between application code, configuration, and exploit logic. No fake or destructive payloads are present; the exploit is a safe, operational PoC for RCE.flame-11 · Disclosed Jan 8, 2026 · python · php · networkOperationalCVE-2025-54068Single-file Python exploit tool targeting CVE-2025-54068 against Laravel Livewire applications. The repository contains one substantial script, CVE-2025-54068.py, which implements an end-to-end exploitation workflow rather than a simple detector. The code imports requests, BeautifulSoup, AES/Crypto primitives, threading, subprocess, and concurrent execution modules, indicating automated HTTP interaction, HTML parsing, Laravel-style cryptographic payload handling, and mass exploitation support. The script structure includes: large constant tables for Livewire version fingerprinting (mapping many Livewire 3.x versions to identifiers), default .env discovery paths for APP_KEY harvesting, candidate writable directories for file-drop/web-shell placement, dangerous constructor metadata, and multiple gadget-chain templates for PHP object deserialization. The visible menu logic shows three operating modes: exploit a single URL, exploit targets from file(s) in bulk, and APP_KEY discovery only. It also supports non-interactive/automated execution via environment-driven configuration and can spawn multiple processes for mass exploitation. Primary capabilities inferred from the code are: fingerprinting Livewire versions, probing common Laravel .env locations to recover APP_KEY values, generating encrypted/signed Laravel-compatible payloads, selecting among several gadget chains, and attempting RCE or file-write outcomes on vulnerable targets. The writable-directory list strongly suggests support for dropping a shell or other attacker-controlled file into web-accessible locations. Because the exploit includes actual payload construction and operational workflow, it is best classified as an operational exploit rather than a proof-of-concept. Fingerprintable observables in the code are mostly target-side file paths rather than hardcoded remote infrastructure: numerous .env probe paths and common Laravel writable/public directories. No fixed attacker-controlled IPs or domains are visible in the provided content. The script appears intended for arbitrary operator-supplied target URLs over HTTP/HTTPS rather than a single hardcoded endpoint.zycoder0day · Disclosed May 11, 2026 · python · web · networkOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LaravelLivewireapplication
FAQ

Frequently asked questions

Is CVE-2025-54068 exploited in the wild?
Yes. As of Oct 31, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 20, 2026.
Is there a public exploit for CVE-2025-54068?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2025-54068, the earliest disclosed Dec 23, 2025.
Is there a patch for CVE-2025-54068?
Upgrade affected Livewire v3 installations to version 3.6.4 or a later supported release. The corrected hydration logic preserves the original raw snapshot context during recursive updates.
What products are affected by CVE-2025-54068?
Laravel Livewire.
How severe is CVE-2025-54068?
CVE-2025-54068 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 96.3% (100th percentile) as of Oct 31, 2026.
Activity feed

Recent activity

64 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence8Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity42Community discussion across Reddit, Mastodon, and other social sources.