Simple Restrict < 1.2.9 - Authenticated (Contributor+) Information Exposure
Strategic Overview
- Status
- Patched in 1.2.9
- Affected Plugin
- Simple Restrict
- Affected Version
< 1.2.9- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-15939
At a glance
CVE-2026-15939 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Simple Restrict WordPress plugin, affecting versions < 1.2.9. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.2.9; sites on affected versions should update now. Disclosed July 2026, reported by Shikhali Jamalzade (alisalive).
Vulnerability Overview
The Simple Restrict plugin for WordPress is vulnerable to Information Exposure in all versions up to 1.2.9 (exclusive) via the REST API due to insufficient restrictions on which posts can be included. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract data from password protected, private, or draft posts that they should not have access to.
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 interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Simple Restrict < 1.2.9 takes an account at Contributor level or above. 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 Simple Restrict the fix is 1.2.9: builds < 1.2.9 are affected, anything from 1.2.9 onward is not.
Remediation
Update to version 1.2.9, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Simple Restrict 1.2.9 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C