# PPWP <= 1.9.28 - Unauthenticated Sensitive Information Exposure via REST API

- **ID:** WPSEC-2026-3631
- **Plugin:** PPWP – Password Protect Pages (`password-protect-page`), https://wordpress.org/plugins/password-protect-page/
- **Affected versions:** from 1.7.9 before 1.9.29
- **Fixed in:** 1.9.29 (Update to 1.9.29 or later.)
- **Severity:** Medium 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N)
- **Weakness:** CWE-200
- **Usage among sites WPSec scans:** plugin Low, affected versions None seen (as of 2026-11-21)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/password-protect-page
- **Fix released:** 2026-11-20
- **Published:** 2026-11-21
- **URL:** https://wpsec.com/vuln/WPSEC-2026-3631/

## Description

The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure via the WordPress REST API routes of the Partial Content Protection section (ppwp-section) post type in all versions up to, and including, 1.9.28. This is due to the post type being registered with show_in_rest enabled while its content is only password-checked when it is rendered through the [ppwp section] shortcode, with no access restriction on its REST routes. This makes it possible for unauthenticated attackers to read the content of password-protected Partial Content Protection sections without providing the required password.

## References

- https://wpsec.com/vuln/WPSEC-2026-3631/
- https://plugins.svn.wordpress.org/password-protect-page/tags/1.9.29/
- https://wordpress.org/plugins/password-protect-page/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-3631/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.
