HomeWordPress vulnerabilitiesPPWP
PPWP vulnerabilities
PPWP has 7 known vulnerabilities in this database. The most recent published record is dated 25 Aug 2026.
- Known vulnerabilities
- 7
- Active installs
- 30,000+
- Latest version
- 1.9.26
- Last updated
- 1 Oct 2026
- Most recent
- 25 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2025-9878 | Medium 6.4 | Up to 1.9.21 | Fixed in a later version (latest 1.9.26) | 25 Aug 2026 |
| PHP object injection CVE-2026-0551 | High 8.8 | Up to 1.9.18 | Fixed in a later version (latest 1.9.26) | 23 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-3639 | Medium 6.4 | Up to 1.9.21 | Fixed in a later version (latest 1.9.26) | 13 Aug 2026 |
| Security weakness CVE-2025-5998 | Medium 6.5 | Before 1.9.11 | Fixed in 1.9.11 | 14 Aug 2025 |
| Sensitive data exposure CVE-2024-11280 | Medium 5.3 | Up to 1.9.5 | Fixed in a later version (latest 1.9.26) | 17 Dec 2024 |
| Sensitive data exposure CVE-2024-0620 | Medium 5.3 | Before 1.9.0 | Fixed in 1.9.0 | 29 Feb 2024 |
| Cross-site scripting (XSS) CVE-2022-4626 | Medium 5.4 | Before 1.8.6 | Fixed in 1.8.6 | 6 Feb 2023 |
Read the published descriptions
- CVE-2025-9878, 25 Aug 2026
- The PPWP - Password Protect WordPress | #1 Most-Reviewed Password Plugin plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ppwp' shortcode in all versions up to, and including, 1.9.21 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2026-0551, 23 Aug 2026
- The PPWP - Password Protect Pages plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.9.18 via deserialization of untrusted input from the 'post_protection_roles' vulnerable parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present. CVE record
- CVE-2026-3639, 13 Aug 2026
- The PPWP - Password Protect Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's `ppwp` shortcode attributes in all versions up to, and including, 1.9.21 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
- CVE-2025-5998, 14 Aug 2025
- The PPWP - Password Protect Pages WordPress plugin before version 1.9.11 allows to put the site content behind a password authorization, however users with subscriber or greater roles can view content via the REST API. CVE record
- CVE-2024-11280, 17 Dec 2024
- The PPWP - Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.9.5 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator. CVE record
- CVE-2024-0620, 29 Feb 2024
- The PPWP - Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.9 via API. This makes it possible for unauthenticated attackers to obtain post titles, IDs, slugs as well as other information including for password-protected posts. CVE record
- CVE-2022-4626, 6 Feb 2023
- The PPWP WordPress plugin before 1.8.6 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks which could be used against high privilege users such as admins. CVE record
What to do if you run PPWP
If you run PPWP, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new PPWP vulnerabilities
Free. We email you when a new vulnerability is published for PPWP, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.