CVE-2024-22859Network attack vector

Disputed code execution via CSRF token caching

Published Feb 1, 2024 · Updated May 29, 2025

The disputed CVE record for Livewire before 3.0.4 states that remote attackers execute arbitrary code through getCsrfToken. The cited commit only stops frontend getCsrfToken from reusing a cached token after a Laravel session token changes, preventing legitimate requests from receiving HTTP 419 responses. Livewire maintainers state that the change fixes a usability defect rather than a security issue, and GitHub withdrew its advisory after reviewing the explanation.

CVSS severity8.8
High
EPSS probability0.46%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

The disputed CVE record for Livewire before 3.0.4 states that remote attackers execute arbitrary code through getCsrfToken. The cited commit only stops frontend getCsrfToken from reusing a cached token after a Laravel session token changes, preventing legitimate requests from receiving HTTP 419 responses. Livewire maintainers state that the change fixes a usability defect rather than a security issue, and GitHub withdrew its advisory after reviewing the explanation.

The record

CVE
CVE-2024-22859
Published
Feb 1, 2024
Updated
May 29, 2025
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-352
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Feb 1, 2024CVE publishedPublication date reported by the CVE source.
  2. May 29, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

8.8CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
8.8GitHubCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-352Cross-Site Request Forgery (CSRF)

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo