# CVE-2025-3453: Information disclosure in Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content

> Unauthenticated attackers can extract all protected site content if the Use Transient setting is enabled in the Password Protected 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:** 17 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-vmhf-wmj5-jx54

## What is CVE-2025-3453?

CVE-2025-3453 is a medium-severity vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 17 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Password Protected – Password Protect your WordPress Site, Pages, & WooCommerce Products – Restrict Content, Protect WooCommerce Category and more plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.7.7 via the 'password_protected_cookie' function. This makes it possible for unauthenticated attackers to extract sensitive data including all protected site content if the 'Use Transient' setting is enabled.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2025-3453?


## How do I fix CVE-2025-3453?

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

## Is CVE-2025-3453 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3453 and fix it if it is affected.

What it is: CVE-2025-3453 is a medium-severity vulnerability in saadiqbal Password Protected — Lock Entire Site, Pages, Posts, Categories, and Partial Content, published on 17 Apr 2025. 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-2025-3453 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-2025-3453/ (Markdown: https://insights.sbomify.com/CVE-2025-3453/index.md)
```

## Sources

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

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