CVE-2026-15939
Simple Restrict < 1.2.9 - Contributor+ Restricted Content Disclosure via REST API
Description
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.
INFO
Published Date :
Aug. 2, 2026, 6:16 a.m.
Last Modified :
Aug. 2, 2026, 6:16 a.m.
Remotely Exploit :
No
Source :
[email protected]
Affected Products
The following products are affected by CVE-2026-15939
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update the Simple Restrict WordPress plugin to 1.2.9 or later.
- Verify plugin permissions and content access.
- Apply vendor-supplied security patches.
- Monitor for unauthorized content access.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-15939.
| URL | Resource |
|---|---|
| https://wpscan.com/vulnerability/307a3033-ca65-4c3a-9a08-dd4a6f7dacea/ |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-15939 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-15939
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-15939 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-15939 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
Aug. 02, 2026
Action Type Old Value New Value Added Affected [{'vendor': 'Unknown', 'product': 'Simple Restrict', 'versions': [{'status': 'affected', 'version': '0', 'lessThan': '1.2.9', 'versionType': 'semver'}], 'defaultStatus': 'unaffected'}] Added Description 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. Added Reference https://wpscan.com/vulnerability/307a3033-ca65-4c3a-9a08-dd4a6f7dacea/