Private Content
private-content · plugin
Known security vulnerabilities for Private Content. Find out in seconds which version runs on your site with WP Lens.
5 known vulnerabilities
2 critical · 3 exploitable without logging in · latest Jul 1, 2026
Closed on wordpress.org
Removed from the directory on Sep 10, 2022 · reason: author request. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- Critical 9.8
CVE-2026-57692unauthenticated≤ 9.9.2
WordPress PrivateContent plugin <= 9.9.2 - Privilege Escalation vulnerability
- Critical 9.8
CVE-2025-26966unauthenticated≤ 8.11.5
WordPress PrivateContent plugin <= 8.11.5 - Unauthenticated Account Takeover vulnerability
- High 8.5
CVE-2025-26976login required≤ 8.11.4
WordPress PrivateContent plugin <= 8.11.4 - SQL Injection vulnerability
- High 8.3
CVE-2025-26969subscriber+≤ 8.11.5
WordPress PrivateContent plugin <= 8.11.5 - Subscriber+ Site Wide Broken Access Control vulnerability
- High 7.1
CVE-2025-26972unauthenticated · needs a click≤ 8.11.5
WordPress PrivateContent plugin <= 8.11.5 - Reflected Cross Site Scripting (XSS) vulnerability
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).