CVE-2026-0551 HIGH

CVE-2026-0551: PPWP – Password Protect Pages <= 1.9.18 - Authenticated (Contributor+) PHP Object Injection via post_protection_roles

Vendor Buildwps
Product PPWP – Password Protect Pages
Weakness CWE-502 · Unsafe deserialization
Published August 22, 2026
Last update August 22, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

PPWP – Password Protect Pages versions up to 1.9.18 contain a deserialization vulnerability that allows authenticated users to execute arbitrary PHP code on the site. An attacker with low-level access can craft malicious serialized data to trigger code execution. This affects all installations running the vulnerable version range.

What an attacker can do

03Attacker Capabilities

Run arbitrary PHP code on the site and take full control of it.

Potential impact on your site

04Site Impact

Any authenticated user can compromise your entire site, including database access and file modification.

Conditions required to exploit

05Prerequisites

Attacker must have a low-level user account (subscriber or contributor role or equivalent).

Key dates

06Disclosure timeline

August 22, 2026 CVE published

Related vulnerabilities

08Related CVE