# CVE-2026-90952: WP Edit Password Protected 2.0.0 - 2.0.6 - Unauthenticated Site-Wide Access Mode Bypass via REST API

> Unauthenticated attackers can bypass site-wide access restrictions via the REST API to read hidden published content in the WP Edit Password Protected plugin.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Oct 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-phjc-p22w-v899

## What is CVE-2026-90952?

CVE-2026-90952 is a medium-severity missing authorization vulnerability in Unknown WP Edit Password Protected, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Edit Password Protected WordPress plugin before 2.0.7 does not enforce its site-wide access restriction on the WordPress REST API, allowing unauthenticated users to read the content of published posts and pages that the site's access mode was configured to hide.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-90952 being exploited?

There is no known exploitation of CVE-2026-90952 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-90952 is a medium-severity missing authorization vulnerability in Unknown WP Edit Password Protected, published on 2 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-90952 in the wild and no public exploit code.

Affected product: Unknown WP Edit Password Protected. 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-90952/ (Markdown: https://insights.sbomify.com/CVE-2026-90952/index.md)
```

## Sources

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

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