Signal is active with 3 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
CVE-2026-15939 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 … https://www.cve.org/CVERecord?id=CVE-2026-15939
Post summary
CVE-2026-15939 identifies a permission-check flaw in the Simple Restrict WordPress plugin affecting the REST API; no PoC, exploit, or mitigation details are included.
🚨*CVE* CVE-2026-15939 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 … https://www.cve.org/CVERecord?id=CVE-2026-15939 ----- Traducción: CVE-2026-15939 El … http://infoflow.cloud`
Post summary
The tweet announces CVE-2026-15939, highlighting a permission‑check flaw in the Simple Restrict WordPress plugin before 1.2.9, and links to the CVE record, but provides no PoC, exploit, or patch information.
CVE-2026-15939 Unauthorized Restricted Content Access in Simple Restrict WordPress Plugin Before 1.2.9 https://vulmon.com/vulnerabilitydetails?qid=CVE-2026-15939
Post summary
The text announces CVE-2026-15939, a vulnerability in Simple Restrict WordPress Plugin allowing unauthorized restricted content access prior to version 1.2.9.