CSRF protection bypass via predictable token generation
Published Jun 11, 2025 · Updated Jun 11, 2025
Weak CSRF token generation in Mojolicious::Plugin::CSRF 1.03 allows remote attackers to predict tokens and bypass request validation. The token generator hashes the process ID, current time, and one Perl rand() result with MD5 instead of using cryptographically secure randomness. Exploitation depends on an application using these tokens for CSRF protection and enables forged state-changing requests within the victim's authorized session.
Summary
What happened
Weak CSRF token generation in Mojolicious::Plugin::CSRF 1.03 allows remote attackers to predict tokens and bypass request validation. The token generator hashes the process ID, current time, and one Perl rand() result with MD5 instead of using cryptographically secure randomness. Exploitation depends on an application using these tokens for CSRF protection and enables forged state-changing requests within the victim's authorized session.
The record
- CVE
- CVE-2025-40915
- Published
- Jun 11, 2025
- Updated
- Jun 11, 2025
- Vendor
- Gryphon Shafer
- Product
- Mojolicious::Plugin::CSRF
- Classifications
- CWE-338, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 11, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 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=1.03
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