Skip to main content
VulnerabilityPublished Updated

CVE-2024-22859: Cross-Site Request Forgery (CSRF)

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High : upgrade to 3.0.4 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Feb 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade livewire/livewire to 3.0.4.

Affected software

ProductAffectedFixed in
GitHublivewire/livewirepkg:github/livewire/livewireOther threatsAffected
  • <3.0.4
Fixed in
  • 3.0.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should first identify whether their web applications use Livewire versions prior to 3.0.4. If so, upgrading to version 3.0.4 or later is the most effective mitigation, as it addresses the reported issue. In the absence of a vendor patch or if upgrade is not immediately feasible, organizations should implement strict CSRF protections, including validating CSRF tokens on all state-changing requests and enforcing same-site cookie attributes. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF attack patterns. Additionally, monitoring web server logs for unusual POST requests or HTTP 419 status codes may help detect exploitation attempts. Educating developers and administrators about secure coding practices related to CSRF prevention is crucial. Given the vendor's dispute, organizations should also conduct their own security assessments or penetration tests to verify the vulnerability's presence and impact in their environment. Finally, maintaining up-to-date backups and incident response plans will help mitigate potential damage from exploitation.

Description

Cross-Site Request Forgery (CSRF) vulnerability in livewire before v3.0.4, allows remote attackers to execute arbitrary code getCsrfToken function. NOTE: the vendor disputes this because the 5d88731 commit fixes a usability problem (HTTP 419 status codes for legitimate client activity), not a security problem.

References

Community reviews

Loading reviews…