CVE-2025-8945

Edit Password Protected <= 1.3.4 - Unauthenticated Protection Bypass

2025-08-21 00:00
Pierre Rudloff

Strategic Overview

Status
Patched in 1.3.5
Affected Version
<= 1.3.4
CVSS
4.3Medium
Weakness type
CWE-693 · Protection Mechanism Failure
CVE
CVE-2025-8945
View all WPEPP – Essential Security, Password Protect & Login Page Customizer vulnerabilities

At a glance

CVE-2025-8945 is a medium-severity Protection Mechanism Failure vulnerability in the WPEPP WordPress plugin, affecting versions <= 1.3.4. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.5; sites on affected versions should update now. Disclosed August 2025, reported by Pierre Rudloff.

Vulnerability Overview

The WPEPP – Essential Security, Password Protect & Login Page Customizer plugin for WordPress is vulnerable to Protection Bypass in all versions up to, and including, 1.3.4. This makes it possible for authenticated attackers, with Custom-level access and above, to view password protected content via REST API.

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 interaction from a victim user.

CWE-693: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

Remediation

Update to version 1.3.5, 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: WPEPP 1.3.5 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