Skip to main content
VulnerabilityPublished

CVE-2025-40915: GRYPHON Mojolicious::Plugin::CSRF · Use of Cryptographically Weak Pseudo-Random Number Generator

Affects GRYPHON Mojolicious::Plugin::CSRFSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High.

Data as of 26 Oct 2026, 10:12 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Jun 2025

  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

Affected software

ProductAffectedFixed in
GRYPHON Mojolicious::Plugin::CSRFAffected
  • =1.03
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately upgrade to a patched version of Mojolicious::Plugin::CSRF once available, or apply vendor-provided patches if released. In the absence of official patches, developers should replace the token generation logic with a cryptographically secure PRNG, such as those provided by the Crypt::PRNG or Crypt::Random Perl modules, and avoid using predictable entropy sources like process IDs or timestamps. Additionally, switching from MD5 to a stronger hash function like SHA-256 or SHA-3 for token generation is recommended. Web application firewalls (WAFs) can be configured to detect and block suspicious CSRF token patterns or anomalous request behaviors as a temporary measure. Organizations should also conduct code audits to identify other instances of weak randomness and enforce secure coding standards for cryptographic operations. Finally, educating developers about secure token generation and regularly updating dependencies will reduce future risks.

Description

Mojolicious::Plugin::CSRF 1.03 for Perl uses a weak random number source for generating CSRF tokens. That version of the module generates tokens as an MD5 of the process id, the current time, and a single call to the built-in rand() function.

References

Community reviews

Loading reviews…