HomeWordPress vulnerabilitiesSimple Restrict
Simple Restrict vulnerabilities
Simple Restrict has 3 known vulnerabilities in this database. The most recent published record is dated 2 Aug 2026.
- Known vulnerabilities
- 3
- Active installs
- 1,000+
- Latest version
- 1.2.9
- Last updated
- 15 Jul 2026
- Most recent
- 2 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-15939 | Low 2.7 | Before 1.2.9 | Fixed in 1.2.9 | 2 Aug 2026 |
| Sensitive data exposure CVE-2024-11106 | Medium 5.3 | Up to 1.2.7 | Fixed in a later version (latest 1.2.9) | 10 Dec 2024 |
| Sensitive data exposure CVE-2024-1083 | Medium 5.3 | Before 1.2.7 | Fixed in 1.2.7 | 13 Mar 2024 |
Read the published descriptions
- CVE-2026-15939, 2 Aug 2026
- The Simple Restrict WordPress plugin before 1.2.9 does not enforce its content-restriction permission check on the REST API the way it does on the front end, relying there on a generic capability check instead of the Simple Restrict WordPress plugin before 1.2.9's own permission system, allowing users with contributor-level access or above to read the content of restricted posts and pages they were never granted access to. CVE record
- CVE-2024-11106, 10 Dec 2024
- The Simple Restrict plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.7 via the WordPress core search feature. This makes it possible for unauthenticated attackers to extract sensitive data from posts that have been restricted to higher-level roles such as administrator. CVE record
- CVE-2024-1083, 13 Mar 2024
- The Simple Restrict plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.2.6 via the REST API. This makes it possible for authenticated attackers to bypass the plugin's restrictions to extract post titles and content CVE record
What to do if you run Simple Restrict
If you run Simple Restrict, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Simple Restrict vulnerabilities
Free. We email you when a new vulnerability is published for Simple Restrict, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.