dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-27517

CRITICAL · 9.3 CVSS v4.0 Published 2025-03-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Volt is an elegantly crafted functional API for Livewire. Malicious, user-crafted request payloads could potentially lead to remote code execution within Volt components. This vulnerability is fixed in 1.7.0.

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 · moderate confidence

Volt is a functional API for Livewire (Laravel). The vulnerability allows attackers to send malicious crafted request payloads to Volt components, achieving remote code execution. This is a critical code injection issue in the Volt framework's request handling logic.

MitigationUpgrade Volt to version 1.7.0 or later. Audit existing Volt components for any signs of compromise and implement input validation as a defense-in-depth measure.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Volt package version
    Run `composer show livewire/volt` or inspect the `composer.json` file's `require` section for the livewire/volt entry
    Affected if The installed version is lower than 1.7.0 (e.g., 1.0.0 through 1.6.x)
  2. Verify Volt components are registered
    Inspect the `bootstrap/app.php` or service provider file for Volt::component() registrations, or check the `app/Livewire` directory for .php component files
    Affected if Volt components exist in the application (the vulnerability only affects applications using Volt)
  3. Confirm Volt routes are exposed
    Examine `routes/web.php` or `routes/api.php` for Route::volt() or Livewire route definitions that expose Volt components to HTTP requests
    Affected if Volt components are mounted and accessible via web or API routes (the flaw is exploitable through HTTP request handling)
  4. Review component class structure
    Open a few Volt component files in the app and verify they use the Volt functional API (the `Volt::route()` or class-based Livewire components with Volt features)
    Affected if The application uses Volt's functional API for Livewire (code injection occurs in Volt's request handling logic)
  5. Check Laravel and Livewire versions
    Run `composer show` to confirm Livewire version, as Volt depends on Livewire
    Affected if Livewire is present (Volt integrates with Livewire's request processing)
  6. Audit recent access logs
    Review web server access logs for unusual POST requests to Volt component endpoints with unexpected PHP serialized or encoded payloads
    Affected if Suspicious requests targeting Volt endpoints are found in logs (indicates potential exploitation attempts)

Your environment is affected if Volt version is below 1.7.0 AND Volt components are exposed via HTTP routes, as the code injection occurs in Volt's request handling logic when processing incoming requests.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Volt to version 1.7.0 or later. Audit existing Volt components for any signs of compromise and implement input validation as a defense-in-depth measure.

Recommended fix Moderate confidence

1.7.0

  1. Upgrade the Volt package for Livewire to version 1.7.0 or later
  2. Run composer update livewire/volt or composer require livewire/volt:^1.7.0 to install the fixed version
  3. Verify the upgrade by checking composer.json or running composer show livewire/volt to confirm the installed version
  4. Test your application thoroughly after upgrading to ensure Volt components function correctly with the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27517 — 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-27517 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