Live › vulnerability › CVE-2026-116520
The PPWP Password Protect Pages WordPress plugin up to and including 1.9.26 fails to sanitize the desc_below_form shortcode attribute, so text submitted through comments is stored and rendered unescaped. An unauthenticated attacker can get scripts to run in the browser of anyone who opens an affected protected page.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-31 06:33 UTC. All times on this page are UTC.
Sites running the PPWP Password Protect Pages plugin at version 1.9.26 or earlier that use the comment shortcode with desc_below_form on password-protected pages. Sites without this plugin or running a later version are not affected per the sources.
No product ranges from the sources yet.
wp plugin get ppwp-password-protect-pages --field=version (slug assumed; confirm it).1.9.26; the fixed version number is not stated in the sources.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'comment / shortcode attribute desc_below_form (and placeholder as the marker-smuggling helper)' parameter in all versions up to, and including, 1.9.26 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is exploitable by unauthenticated attackers because WordPress's comment_content filter leaves bare shortcode text (containing no HTML tags) untouched, and the comment_whitelist setting auto-approves subsequent comments from a previously approved name and email without administrator intervention.
This page as .md · .json · in your agent: get_signal("CVE-2026-116520")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.