WordPress plugin · Updated daily · Source: Wordfence Intelligence

PPWP vulnerabilities: affected versions and fixes

PPWP has 30,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

PPWP at a glance

  • 12 publicly disclosed vulnerabilities, 2 of them rated High or Critical. The most recent was disclosed on Oct 30, 2026.
  • Ranked #983 by popularity on WordPress.org (30,000+ active installs).
  • The latest version is 1.9.29 (released Nov 20, 2026). The most recent security fix shipped in 1.9.27.
  • Every disclosed vulnerability has a fix. If you are on the latest version, none of them apply to you.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your PPWP version

Enter the PPWP version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “PPWP”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “PPWP”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (1.9.29). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known PPWP vulnerabilities

  • PPWP <= 1.9.26 - Unauthenticated Stored Cross-Site Scripting via '[ppwp]' Shortcode 'desc_below_form' Attribute via Placeholder Marker Collision

    Cross-site scripting (XSS) · CVE-2026-116520

    Affected versions: ≤ 1.9.26

    Fixed in: 1.9.27

    Severity: High 7.2 · Disclosed Oct 30, 2026

  • Password Protect WordPress Lite <= 1.9.21 - Authenticated (Contributor+) Stored Cross-Site Scripting

    Cross-site scripting (XSS) · CVE-2025-9878

    Affected versions: ≤ 1.9.21

    Fixed in: 1.9.22

    Severity: Medium 6.4 · Disclosed Aug 24, 2026

  • PPWP – Password Protect Pages <= 1.9.18 - Authenticated (Contributor+) PHP Object Injection via post_protection_roles

    PHP object injection · CVE-2026-0551

    Affected versions: ≤ 1.9.18

    Fixed in: 1.9.19

    Severity: High 8.8 · Disclosed Aug 22, 2026

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

    Missing authorization · CVE-2025-11729

    Affected versions: ≤ 1.9.15

    Fixed in: 1.9.16

    Severity: Medium 4.3 · Disclosed Aug 18, 2026

  • Password Protect WordPress Lite <= 1.9.20 - Insecure Direct Object Reference to Authenticated (Contributor+) Password Protected Post Password Update

    Missing authorization · CVE-2025-10005

    Affected versions: ≤ 1.9.20

    Fixed in: 1.9.21

    Severity: Medium 4.3 · Disclosed Aug 15, 2026

  • PPWP – Password Protect Pages <= 1.9.21 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

    Cross-site scripting (XSS) · CVE-2026-3639

    Affected versions: ≤ 1.9.21

    Fixed in: 1.9.22

    Severity: Medium 6.4 · Disclosed Aug 12, 2026

  • PPWP – Password Protect Pages <= 1.9.19 - Authenticated (Contributor+) Insecure Direct Object Reference

    Missing authorization · CVE-2026-57634

    Affected versions: ≤ 1.9.19

    Fixed in: 1.9.20

    Severity: Medium 4.3 · Disclosed Jun 26, 2026

  • PPWP – Password Protect Pages <= 1.9.15 - Missing Authorization

    Missing authorization · CVE-2026-32562

    Affected versions: ≤ 1.9.15

    Fixed in: 1.9.16

    Severity: Medium 4.3 · Disclosed Mar 23, 2026

  • PPWP – Password Protect Pages <= 1.9.10 - Authenticated (Subscriber+) Content Exposure via REST API

    Other weakness · CVE-2025-5998

    Affected versions: ≤ 1.9.10

    Fixed in: 1.9.11

    Severity: Medium 4.3 · Disclosed Aug 25, 2025

  • PPWP – Password Protect Pages <= 1.9.5 - Unauthenticated Content Restriction Bypass to Sensitive Information Exposure

    Information disclosure · CVE-2024-11280

    Affected versions: ≤ 1.9.5

    Fixed in: 1.9.6

    Severity: Medium 5.3 · Disclosed Dec 16, 2024

  • PPWP – Password Protect Pages <= 1.8.9 - Protection Mechanism Bypass

    Other weakness · CVE-2024-0620

    Affected versions: ≤ 1.8.9

    Fixed in: 1.9.0

    Severity: Medium 5.3 · Disclosed Feb 7, 2024

  • PPWP – WordPress Password Protect Page <= 1.8.5 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode

    Cross-site scripting (XSS) · CVE-2022-4626

    Affected versions: ≤ 1.8.5

    Fixed in: 1.8.6

    Severity: Medium 6.4 · Disclosed Jan 10, 2023

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Oct 30, 2026.

Most common weaknesses in PPWP

Cross-site scripting (XSS)

4 issues

An attacker plants a malicious script on a page so that it runs in visitors’ browsers. If an administrator opens that page, the attacker can steal their session or act as the administrator.

Missing authorization

4 issues

Actions that should require a login or a particular role can be carried out without the proper check. Attackers use this to change settings or read data they should not see.

PHP object injection

1 issue

Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.

Frequently asked questions

Is PPWP safe to use?

PPWP is a well-known plugin with 30,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (1.9.29) and turn on automatic updates.

How do I find which version of PPWP my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesPPWP on WordPress.org