# CVE-2016-9479: Auth bypass in n/a

> Remote attackers can reset arbitrary user passwords via the lost password functionality, leading to account takeover.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Dec 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r7c5-pm6v-r8j9

## What is CVE-2016-9479?

CVE-2016-9479 is a high-severity authentication bypass vulnerability in n/a, published on 2 Dec 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The "lost password" functionality in b2evolution before 6.7.9 allows remote attackers to reset arbitrary user passwords via a crafted request.

Weakness: CWE-255

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

It affects 1 product.


Products: B2evolution B2evolution.

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

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

## Is CVE-2016-9479 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-8901](https://insights.sbomify.com/CVE-2016-8901/): Deserialization in n/a (critical 9.8)
- [CVE-2017-1000423](https://insights.sbomify.com/CVE-2017-1000423/): Code injection in n/a (critical 9.8)
- [CVE-2022-30935](https://insights.sbomify.com/CVE-2022-30935/): Auth bypass in n/a (critical 9.1)
- [CVE-2017-5539](https://insights.sbomify.com/CVE-2017-5539/): Path traversal in n/a (critical 9.1)
- [CVE-2021-28242](https://insights.sbomify.com/CVE-2021-28242/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9479 and fix it if it is affected.

What it is: CVE-2016-9479 is a high-severity authentication bypass vulnerability in n/a, published on 2 Dec 2016. 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-9479 in the wild and no public exploit code.

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

## Sources

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

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