CVE-2025-3924

PeproDev Ultimate Profile Solutions 1.9.1 - 7.5.2 - Missing Authorization to Unauthenticated Email Enumeration

2025-05-06 13:27
kr0d

Strategic Overview

Status
Patched in 8.0.0
Affected Version
1.9.1 – 7.5.2
CVSS
5.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-3924
View all PeproDev Ultimate Profile Solutions vulnerabilities

At a glance

CVE-2025-3924 is a medium-severity Improper Authorization vulnerability in the PeproDev Ultimate Profile Solutions WordPress plugin, affecting versions 1.9.1 – 7.5.2. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.0.0; sites on affected versions should update now. Disclosed May 2025, reported by kr0d.

Vulnerability Overview

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.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-285: Improper Authorization

PeproDev Ultimate Profile Solutions 1.9.1 – 7.5.2 carries this weakness at valid_email, and reaching it takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For PeproDev Ultimate Profile Solutions the fix is 8.0.0: builds 1.9.1 – 7.5.2 are affected, anything from 8.0.0 onward is not.

Remediation

Update to version 8.0.0, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PeproDev Ultimate Profile Solutions 8.0.0 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C