CSRF bypass via accepted empty token pair
Published Feb 13, 2024 · Updated Apr 24, 2025
CSRF bypass in Plack::Middleware::XSRFBlock before 0.0.19 allows remote attackers to submit state-changing requests through a victim browser. The detect_xsrf routine treats an empty form token and an empty cookie as matching values instead of rejecting the missing token pair. Exploitation requires user interaction and an application configured without signed cookies; resulting actions are limited to those the victim is authorized to perform.
Summary
What happened
CSRF bypass in Plack::Middleware::XSRFBlock before 0.0.19 allows remote attackers to submit state-changing requests through a victim browser. The detect_xsrf routine treats an empty form token and an empty cookie as matching values instead of rejecting the missing token pair. Exploitation requires user interaction and an application configured without signed cookies; resulting actions are limited to those the victim is authorized to perform.
The record
- CVE
- CVE-2023-52431
- Published
- Feb 13, 2024
- Updated
- Apr 24, 2025
- Vendor
- Plack Middleware
- Product
- Plack::Middleware::XSRFBlock
- Classifications
- CWE-269, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 13, 2024CVE publishedPublication date reported by the CVE source.
- Apr 24, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.0.19
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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