CVE-2025-27517
Published: 05 March 2025
Summary
CVE-2025-27517 is a critical-severity Improper Input Validation (CWE-20) vulnerability. Its CVSS base score is 9.3 (Critical).
Operationally, ranked in the top 18.7% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Volt is a functional API for Livewire that allows developers to define components using PHP closures. CVE-2025-27517 is an improper input validation flaw (CWE-20) in Volt that permits remote code execution when an application processes malicious, user-supplied request payloads. The vulnerability affects all versions prior to the 1.7.0 release and carries a CVSS 4.0 score of 9.3.
An unauthenticated attacker can send a crafted HTTP request directly to any Volt component endpoint. Successful exploitation grants arbitrary code execution within the context of the affected application, with no user interaction or special privileges required.
The official advisory published in the Livewire Volt repository states that the issue is resolved in version 1.7.0. The EPSS score rose from a low baseline to a recorded peak of 0.0355, indicating emerging exploitation interest after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6154
Vulnerability details
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.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Directly implements checks on information inputs to reject invalid data before processing.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.