WordPress plugin
My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 3 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High1
- Medium2
- Low0
All My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Cross-Site Request Forgery ≤3.0.7Update to 3.0.8 | CVE-2022-1627 |
- High8.8Cross-Site Request Forgery
≤3.0.7Update to 3.0.8
My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam: common questions
Does My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam: 1 high, 2 medium. None are known to affect version null.
How do I check which version of My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam vulnerability?
CVE-2026-81348, published Sep 5, 2026: My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam < 4.2.3 - Unauthenticated Information Exposure. Severity: Medium (CVSS 5.3).
Is any My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam vulnerability listed in CISA KEV?
No. None of the known My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam vulnerabilities is currently listed in the CISA KEV catalog.