# CVE-2012-5686: Weak cryptography in n/a

> Attackers can predict password reset tokens due to insufficient entropy, leading to unauthorized account takeover in ZPanel.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/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:** 4 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-mx36-j5gv-jj56

## What is CVE-2012-5686?

CVE-2012-5686 is a critical vulnerability in n/a, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZPanel 10.0.1 has insufficient entropy for its password reset process.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2012-5686?

It affects 1 product.


Products: Zpanelcp Zpanel.

## How do I fix CVE-2012-5686?

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

## Is CVE-2012-5686 being exploited?

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

Public exploit code:

- ZPanel 10.0.1 - Cross-Site Request Forgery / Cross-Site Scripting / SQL Injection / Password Reset (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-5685](https://insights.sbomify.com/CVE-2012-5685/): SQL injection in n/a (high 7.5)
- [CVE-2012-6654](https://insights.sbomify.com/CVE-2012-6654/): SQL injection in n/a (high 7.5)
- [CVE-2012-5683](https://insights.sbomify.com/CVE-2012-5683/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2012-5684](https://insights.sbomify.com/CVE-2012-5684/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5686 and fix it if it is affected.

What it is: CVE-2012-5686 is a critical vulnerability in n/a, published on 4 Feb 2020. 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-2012-5686 exists.

Affected product: n/a. 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-2012-5686/ (Markdown: https://insights.sbomify.com/CVE-2012-5686/index.md)
```

## Sources

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

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