dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Apr 2026.
LivewireFramework / library · Laravel

CVE-2025-54068

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-17
Fix available
A fix is available. Upgrade to 3.6.4 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Livewire is a full-stack framework for Laravel. In Livewire v3 up to and including v3.6.3, a vulnerability allows unauthenticated attackers to achieve remote command execution in specific scenarios. The issue stems from how certain component property updates are hydrated. This vulnerability is unique to Livewire v3 and does not affect prior major versions. Exploitation requires a component to be mounted and configured in a particular way, but does not require authentication or user interaction. This issue has been patched in Livewire v3.6.4. All users are strongly encouraged to upgrade to this version or later as soon as possible. No known workarounds are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Livewire v3 contains a remote command execution vulnerability in its component property hydration mechanism. Unauthenticated attackers can achieve RCE without user interaction when a component is mounted in a specific configuration. This is a critical flaw in the framework's deserialization/hydration process unique to v3.

MitigationUpgrade Livewire to v3.6.4 or later immediately as no workarounds exist and the CVSS 9.8 score indicates critical severity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
LivewireFramework / library
Affected:>= 3.0.0, < 3.6.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Livewire version
    Examine your composer.json file or the vendor/composer/installed.json file to find the installed version of the livewire/livewire package
    Affected if The installed version is 3.0.0 or higher but lower than 3.6.4
  2. Identify mounted Livewire components
    Review your application code for Livewire components that use the $mount method or accept mount parameters, as these are the specific component configurations mentioned in the CVE
    Affected if Your application has Livewire components configured with mount properties or parameters
  3. Verify component accessibility
    Check your route definitions and middleware configuration to determine whether mounted Livewire components are accessible without authentication
    Affected if Unauthenticated users can directly access or make requests to mounted Livewire components in your application

You are affected if Livewire version is between 3.0.0 and 3.6.3 and your application has mounted Livewire components accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.6.4 or later
Fixed in 3.6.4
Vendor patch github.com →
Interim mitigation

Upgrade Livewire to v3.6.4 or later immediately as no workarounds exist and the CVSS 9.8 score indicates critical severity.

Recommended fix High confidence

Livewire v3.6.4 or later

  1. Ensure your Laravel project uses Livewire v3 by checking your composer.json dependencies
  2. Run 'composer require livewire/livewire:^3.6.4' or 'composer update livewire/livewire' to upgrade to the patched version
  3. Verify the installed version with 'composer show livewire/livewire' to confirm version 3.6.4 or higher is installed
  4. Clear any cached configurations with 'php artisan config:clear' and 'php artisan cache:clear'
  5. Test your application thoroughly after upgrading to ensure Livewire components function correctly
Caveat Minor version upgrades in Livewire may include breaking changes; review the CHANGELOG before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Livewire Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54068 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54068 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data