CVE-2025-11729

PPWP: Password Protect Pages, Posts & Full or Partial Content <= 1.9.15 - Improper Authorization To Authenticated (Contributor+) Master Password Exposure

2026-08-18 11:03
Athiwat Tiprasaharn (Jitlada)

Strategic Overview

Status
Patched in 1.9.16
Affected Plugin
PPWP – Password Protect Pages
Affected Version
<= 1.9.15
CVSS
4.3Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE-2025-11729
View all PPWP – Password Protect Pages vulnerabilities

At a glance

CVE-2025-11729 is a medium-severity Improper Authorization vulnerability in the PPWP WordPress plugin, affecting versions <= 1.9.15. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.9.16; sites on affected versions should update now. Disclosed August 2026, reported by Athiwat Tiprasaharn (Jitlada).

Vulnerability Overview

The PPWP: Password Protect Pages, Posts & Full or Partial Content plugin for WordPress is vulnerable to unauthorized access of data due to a improper capability check on the can_access function in all versions up to, and including, 1.9.15. This makes it possible for authenticated attackers, with Contributor-level access and above, to retrieve a master-password and access any password-protected content.

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-285: Improper Authorization

Reaching this weakness in PPWP <= 1.9.15 takes an account at Contributor level or above. 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 PPWP the fix is 1.9.16: builds <= 1.9.15 are affected, anything from 1.9.16 onward is not.

Remediation

Update to version 1.9.16, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: PPWP 1.9.16 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-11729https://www.wordfence.com/threat-intel/vulnerabilities/id/d1e041f0-3019-4d1f-b1a3-b40275c0966ahttps://nvd.nist.gov/vuln/detail/CVE-2025-11729

Related records

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