# CVE-2025-62512: Piwigo Vulnerable to User Enumeration via Password Reset Endpoint

> Unauthenticated attackers can enumerate valid usernames or emails via distinct responses from the password reset endpoint in Piwigo.

- **Severity:** Medium 5.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-h4wx-7m83-xfxc

## What is CVE-2025-62512?

CVE-2025-62512 is a medium-severity vulnerability in Piwigo Piwigo, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Piwigo is an open source photo gallery application for the web. In version 15.5.0 and likely earlier 15.x releases, the password reset functionality in Piwigo allows an unauthenticated attacker to determine whether a given username or email address exists in the system. The endpoint at password.php?action=lost returns distinct messages for valid vs. invalid accounts, enabling user enumeration. As of time of publication, no known patches are available.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2025-62512?

It affects 1 product.


Products: Piwigo Piwigo.

## How do I fix CVE-2025-62512?

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

## Is CVE-2025-62512 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62512 exists.

Public exploit code:

- Piwigo - User Enumeration via Password Reset (nuclei): http/cves/2025/CVE-2025-62512.yaml

## 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-2025-62512 and fix it if it is affected.

What it is: CVE-2025-62512 is a medium-severity vulnerability in Piwigo Piwigo, published on 24 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-62512 exists.

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-2025-62512/ (Markdown: https://insights.sbomify.com/CVE-2025-62512/index.md)
```

## Sources

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

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