# CVE-2016-3735: Weak cryptography in Piwigo

> An attacker can predict password reset tokens due to weak random number generation, allowing account takeover if an admin email is known.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2022
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-82rp-xg3c-hxpx

## What is CVE-2016-3735?

CVE-2016-3735 is a high-severity vulnerability in Piwigo Piwigo, published on 28 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Piwigo is image gallery software written in PHP. When a criteria is not met on a host, piwigo defaults to usingmt_rand in order to generate password reset tokens. mt_rand output can be predicted after recovering the seed used to generate it. This low an unauthenticated attacker to take over an account providing they know an administrators email address in order to be able to request password reset.

Weakness: CWE-335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2016-3735?

It affects 1 product.


Products: Piwigo Piwigo.

## How do I fix CVE-2016-3735?

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

## Is CVE-2016-3735 being exploited?

There is no known exploitation of CVE-2016-3735 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-2016-3735 and fix it if it is affected.

What it is: CVE-2016-3735 is a high-severity vulnerability in Piwigo Piwigo, published on 28 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-3735 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-2016-3735/ (Markdown: https://insights.sbomify.com/CVE-2016-3735/index.md)
```

## Sources

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

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