# CVE-2025-3924: PeproDev Ultimate Profile Solutions 1.9.1 - 7.5.2 - Missing Authorization to Unauthenticated Email Enumeration

> Unauthenticated attackers can enumerate user email addresses via the reset-password endpoint due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 7 May 2025
- **Updated:** 7 May 2025
- **Also known as:** GHSA-gx79-p29g-9rqw

## What is CVE-2025-3924?

CVE-2025-3924 is a medium-severity missing authorization vulnerability in PeproDev Ultimate Profile Solutions, published on 7 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PeproDev Ultimate Profile Solutions plugin for WordPress is vulnerable to unauthorized access of data via its publicly exposed reset-password endpoint. The plugin looks up the 'valid_email' value based solely on a supplied username parameter, without verifying that the requester is associated with that user account. This allows unauthenticated attackers to enumerate email addresses for any user, including administrators.

Weakness: CWE-285 (Improper Authorization)

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


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

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

## Is CVE-2025-3924 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3924 and fix it if it is affected.

What it is: CVE-2025-3924 is a medium-severity missing authorization vulnerability in PeproDev Ultimate Profile Solutions, published on 7 May 2025. 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-2025-3924 in the wild and no public exploit code.

Affected product: PeproDev Ultimate Profile Solutions. 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-3924/ (Markdown: https://insights.sbomify.com/CVE-2025-3924/index.md)
```

## Sources

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

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