# CVE-2023-4915: WP User Control <= 1.5.3 - Insecure Password Reset Mechanism

> Attackers can trigger unauthorized password resets for any user by providing their email, potentially leading to account takeover if the reset link is intercepted or guessed.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 13 Sep 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xh2m-qfw7-qgvg

## What is CVE-2023-4915?

CVE-2023-4915 is a medium-severity authentication bypass vulnerability in wmsedgar WP User Control, published on 13 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP User Control plugin for WordPress is vulnerable to unauthorized password resets in versions up to, and including 1.5.3. This is due to the plugin using native password reset functionality, with insufficient validation on the password reset function (in the WP User Control Widget). The function changes the user's password after providing the email. The new password is only sent to the user's email, so the attacker does not have access to the new password.

Weakness: CWE-620 (Unverified Password Change)

## Which versions are affected by CVE-2023-4915?

It affects 1 product.


Products: Palmspark Wp User Control.

## How do I fix CVE-2023-4915?

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

## Is CVE-2023-4915 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-4915 and fix it if it is affected.

What it is: CVE-2023-4915 is a medium-severity authentication bypass vulnerability in wmsedgar WP User Control, published on 13 Sep 2023. 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-2023-4915 in the wild and no public exploit code.

Affected product: wmsedgar WP User Control. 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-2023-4915/ (Markdown: https://insights.sbomify.com/CVE-2023-4915/index.md)
```

## Sources

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

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