# CVE-2024-0682: Page Restrict <= 2.5.5 - Protection Mechanism Bypass

> Unauthenticated attackers can view private posts via the REST API due to improper access restrictions in the Page Restrict WordPress 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:** 28 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-hxq4-c5cr-fpxw

## What is CVE-2024-0682?

CVE-2024-0682 is a medium-severity missing authorization vulnerability in sivel Page Restrict, published on 28 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Page Restrict plugin for WordPress is vulnerable to information disclosure in all versions up to, and including, 2.5.5. This is due to the plugin not properly restricting access to posts via the REST API when a page has been made private. This makes it possible for unauthenticated attackers to view protected posts.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2024-0682?

It affects 1 product.


Products: Sivel Page Restrict.

## How do I fix CVE-2024-0682?

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

## Is CVE-2024-0682 being exploited?

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

## Other vulnerabilities in sivel Page Restrict

- [CVE-2024-24702](https://insights.sbomify.com/CVE-2024-24702/): WordPress Page Restrict Plugin <= 2.5.5 is vulnerable to Cross Site Request Forgery (CSRF) (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-0682 and fix it if it is affected.

What it is: CVE-2024-0682 is a medium-severity missing authorization vulnerability in sivel Page Restrict, published on 28 Feb 2024. 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-2024-0682 in the wild and no public exploit code.

Affected product: sivel Page 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-2024-0682/ (Markdown: https://insights.sbomify.com/CVE-2024-0682/index.md)
```

## Sources

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

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