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


- **Severity:** Low 2.7 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-hghg-37rg-7r42

## What is CVE-2024-48928?

CVE-2024-48928 is a low-severity vulnerability in Piwigo Piwigo, published on 24 Feb 2026. 

### Official 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.

Weakness: CWE-330 (Use of Insufficiently Random Values)

## Which versions are affected by CVE-2024-48928?

It affects 1 product.


Products: Piwigo Piwigo.

## How do I fix CVE-2024-48928?

No fix has been published for CVE-2024-48928 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48928 being exploited?

There is no known exploitation of CVE-2024-48928 in the wild and no public exploit code.

## Other vulnerabilities in Piwigo Piwigo

- [CVE-2014-4648](https://insights.sbomify.com/CVE-2014-4648/): Unspecified vulnerability in Piwigo before 2.6.3 has unknown impact and attack vectors, related to a "security failure." (critical 10.0)
- [CVE-2023-33361](https://insights.sbomify.com/CVE-2023-33361/): SQL injection in n/a (critical 9.8)
- [CVE-2023-33362](https://insights.sbomify.com/CVE-2023-33362/): SQL injection in n/a (critical 9.8)
- [CVE-2020-19213](https://insights.sbomify.com/CVE-2020-19213/): SQL injection in n/a (critical 9.8)
- [CVE-2021-32615](https://insights.sbomify.com/CVE-2021-32615/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48928 and fix it if it is affected.

What it is: CVE-2024-48928 is a low-severity vulnerability in Piwigo Piwigo, published on 24 Feb 2026. 
Exploitation: There is no known exploitation of CVE-2024-48928 in the wild and no public exploit code.

Affected product: Piwigo Piwigo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48928/ (Markdown: https://insights.sbomify.com/CVE-2024-48928/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48928
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48928
- OSV: https://osv.dev/vulnerability/CVE-2024-48928

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48928/
Summaries are generated and may contain mistakes; the official description above is the record.