← voltar
CVE-2024-48928

Piwigo's secret key can be brute forced

CVSS 2.7 LOWEPSS 0.3%CWE-330
Vexday Risk Score
8Baixo
Decisão SSVC (CISA)
Track
Sem sinal de exploração → monitorar
CVSS 2.7EPSS 0.3%KEV nãoPoC Nuclei Metasploit Patch
Ciclo de vida
24 fev 2026Publicada no NVD
Recomendação: Monitorar — sem sinal de exploração no momento.
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.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Produtos afetados
Piwigo · Piwigo

Quer saber se a sua infraestrutura está exposta a isto?

Falar com a TrueHacking →