# CVE-2015-10071: gitter-badger ezpublish-modern-legacy forgotpassword.php password recovery

> Weak password recovery in eZ Publish legacy allows attackers to potentially take over user accounts.

- **Severity:** Low 2.6 (`CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qpqg-9qcw-75qc

## What is CVE-2015-10071?

CVE-2015-10071 is a low-severity vulnerability in gitter-badger ezpublish-modern-legacy, published on 19 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was found in gitter-badger ezpublish-modern-legacy. It has been rated as problematic. This issue affects some unknown processing of the file kernel/user/forgotpassword.php. The manipulation leads to weak password recovery. The complexity of an attack is rather high. The exploitation is known to be difficult. Upgrading to version 1.0 is able to address this issue. The patch is named 5908d5ee65fec61ce0e321d586530461a210bf2a. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-218951.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2015-10071?

It affects 1 product.


Products: Gitter Ez Publish Modern Legacy.

## How do I fix CVE-2015-10071?

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

## Is CVE-2015-10071 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10071 and fix it if it is affected.

What it is: CVE-2015-10071 is a low-severity vulnerability in gitter-badger ezpublish-modern-legacy, published on 19 Jan 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-10071 in the wild and no public exploit code.

Affected product: gitter-badger ezpublish-modern-legacy. 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-2015-10071/ (Markdown: https://insights.sbomify.com/CVE-2015-10071/index.md)
```

## Sources

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

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