# CVE-2024-0437: Missing authorization in Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content

> Authenticated subscribers can bypass password protection to read protected post titles and content via the API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-grrx-rcvg-88x9

## What is CVE-2024-0437?

CVE-2024-0437 is a medium-severity missing authorization vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Password Protected – Ultimate Plugin to Password Protect Your WordPress Content with Ease plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.6.6 via the API. This makes it possible for authenticated attackers, with subscriber access or higher, to extract post titles and content, thus bypassing the plugin's password protection.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2024-0437 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0437 is a medium-severity missing authorization vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 14 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0437 in the wild and no public exploit code.

Affected product: saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content. 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-0437/ (Markdown: https://insights.sbomify.com/CVE-2024-0437/index.md)
```

## Sources

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

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