Private Content vulnerabilities
Plugin slug private-content · 6 known vulnerabilities · latest disclosed 2026-07-01 · WordPress.org page
4 vulnerabilities have no fixed version yet. If you use this plugin, consider disabling or replacing it until a fix is released.
2 of 6 rated high or critical (CVSS 7 or more).
Known vulnerabilities in Private Content
| Severity | Affected versions | Fixed in | CVE | Published | Details |
|---|---|---|---|---|---|
| Critical 9.8 | <= 9.9.2 | 9.10.0 | CVE-2026-57692 | 2026-07-01 | Advisory |
| Critical 9.8 | <= 8.11.5 | No fix yet | CVE-2025-26966 | 2025-02-24 | Advisory |
| Medium 6.5 | <= 8.11.5 | No fix yet | CVE-2025-26976 | 2025-02-24 | Advisory |
| Medium 5.4 | <= 8.11.5 | No fix yet | CVE-2025-26969 | 2025-02-24 | Advisory |
| Medium 6.1 | <= 8.11.5 | No fix yet | CVE-2025-26972 | 2025-02-24 | Advisory |
| Medium 5.3 | <= 8.4.3 | 8.4.4 | CVE-2023-0581 | 2023-01-30 | Advisory |
Check if a site is affected
Enter a site address to see which version of Private Content and other plugins it runs, and whether they match a known vulnerability.
Questions
Is the Private Content plugin safe to use?
4 known issue(s) have no fix yet, so check the table above before using it.
How do I check which version of Private Content my site runs?
In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.
How do I fix a vulnerable plugin?
Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.