# CVE-2024-0620: PPWP – Password Protect Pages <= 1.8.9 - Protection Mechanism Bypass

> Unauthenticated attackers can bypass password protection to access sensitive post metadata via the API.

- **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:** 20 Feb 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-mvj6-h82m-cjxf

## What is CVE-2024-0620?

CVE-2024-0620 is a medium-severity vulnerability in buildwps PPWP – Password Protect Pages, published on 20 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The PPWP – Password Protect Pages plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 1.8.9 via API. This makes it possible for unauthenticated attackers to obtain post titles, IDs, slugs as well as other information including for password-protected posts.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Passwordprotectwp Password Protect Wordpress.

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

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

## Is CVE-2024-0620 being exploited?

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

## Other vulnerabilities in buildwps PPWP – Password Protect Pages

- [CVE-2025-5998](https://insights.sbomify.com/CVE-2025-5998/): PPWP < 1.9.11 - Subscriber+ Access Bypass via REST API (medium 6.5)
- [CVE-2022-4626](https://insights.sbomify.com/CVE-2022-4626/): PPWP – WordPress Password Protect Page < 1.8.6 - Contributor+ Stored XSS in Shortcode (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0620 is a medium-severity vulnerability in buildwps PPWP – Password Protect Pages, published on 20 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-0620 in the wild and no public exploit code.

Affected product: buildwps PPWP – Password Protect Pages. 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-0620/ (Markdown: https://insights.sbomify.com/CVE-2024-0620/index.md)
```

## Sources

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

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