My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam < 4.2.3 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 4.2.3
- Affected Plugin
- My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam
- Affected Version
< 4.2.3- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-81348
At a glance
CVE-2026-81348 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the My Private Site WordPress plugin, affecting versions < 4.2.3. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.2.3; sites on affected versions should update now. Disclosed September 2026, reported by Shivamani Vastrala.
Vulnerability Overview
The My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 4.2.3. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in My Private Site < 4.2.3 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For My Private Site the fix is 4.2.3: builds < 4.2.3 are affected, anything from 4.2.3 onward is not.
Remediation
Update to version 4.2.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: My Private Site 4.2.3 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in My Private Site – Make Your Whole Site Private, Force Login & Block Registration Spam
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C