CVE-2025-15578
Received Received - Intake
Insecure Session ID Generation in Maypole Perl

Publication date: 2026-02-16

Last updated on: 2026-03-10

Assigner: CPANSec

Description
Maypole versions from 2.10 through 2.13 for Perl generates session ids insecurely. The session id is seeded with the system time (which is available from HTTP response headers), a call to the built-in rand() function, and the PID.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-02-16
Last Modified
2026-03-10
Generated
2026-06-16
AI Q&A
2026-02-17
EPSS Evaluated
2026-06-15
NVD
EUVD
Affected Vendors & Products
Showing 3 associated CPEs
Vendor Product Version / Range
teejay maypole From 2.10 (inc) to 2.13 (inc)
teejay maypole 2.111
teejay maypole 2.121
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-338 The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

Insecure session ID generation can allow attackers to predict or guess valid session IDs.

This can lead to session hijacking, where an attacker gains unauthorized access to a user's session and potentially sensitive information or functionality.

Such unauthorized access can compromise the confidentiality and integrity of user data and application state.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Executive Summary

This vulnerability affects Maypole versions 2.10 through 2.13 for Perl. It involves the insecure generation of session IDs.

The session ID is created using a seed composed of the system time (which can be obtained from HTTP response headers), a call to the built-in rand() function, and the process ID (PID).

Because these values are predictable or accessible, the session IDs can be guessed or reproduced by an attacker.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-15578. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart