What’s Vulnerable › Vulnerabilities

CVE-2024-48928: Piwigo's secret key can be brute forced

• Severity: high (CVSS 7.5 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.3% probability of exploitation in the next 30 days
• Public exploit or detection template: none known
• Published: 2026-02-24 · updated 2026-06-17
• Weakness: CWE-330

Description

Piwigo is an open source photo gallery application for the web. In versions on the 14.x branch, when installing, the secret_key configuration parameter is set to MD5(RAND()) in MySQL. However, RAND() only has 30 bits of randomness, making it feasible to brute-force the secret key. The CSRF token is constructed partially from the secret key, and this can be used to check if the brute force succeeded. Trying all possible values takes approximately one hour. The impact of this is limited. The auto login key uses the user's password on top of the secret key. The pwg token uses the user's session identifier on top of the secret key. It seems that values for get_ephemeral_key can be generated when one knows the secret key. Version 15.0.0 contains a fix for the issue.

Affected products

• Piwigo: from 14.0.0 through 14.5.0

References

• https://github.com/Piwigo/Piwigo/commit/552499e0533ce54b55f4304b41ca6cd7ccce51f8
• https://github.com/Piwigo/Piwigo/security/advisories/GHSA-hghg-37rg-7r42

Get alerted when CVE-2024-48928 or the next vulnerability affects your stack