# CVE-2026-15939: Simple Restrict < 1.2.9 - Contributor+ Restricted Content Disclosure via REST API

> Contributors can read restricted content via REST API due to missing permission checks in the Simple Restrict WordPress plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Aug 2026
- **Updated:** 5 Aug 2026
- **Also known as:** GHSA-4v4h-6mhp-rwxf

## What is CVE-2026-15939?

CVE-2026-15939 is a low-severity missing authorization vulnerability in Unknown Simple Restrict, published on 2 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-15939?


## How do I fix CVE-2026-15939?

No fix has been published for CVE-2026-15939 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15939 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15939 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15939 and fix it if it is affected.

What it is: CVE-2026-15939 is a low-severity missing authorization vulnerability in Unknown Simple Restrict, published on 2 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-15939 exists.

Affected product: Unknown Simple Restrict. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15939/ (Markdown: https://insights.sbomify.com/CVE-2026-15939/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15939
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15939
- OSV: https://osv.dev/vulnerability/CVE-2026-15939

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15939/
Summaries are generated and may contain mistakes; the official description above is the record.