# CVE-2025-15674: Content Protector (Passster) < 4.3.7 - Contributor+ Protected Content Disclosure via Core REST API

> Contributors can bypass password protection to read protected content via the REST API in the Passster WordPress plugin.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 7 Aug 2026
- **Also known as:** GHSA-wqxf-2hrv-jrwq

## What is CVE-2025-15674?

CVE-2025-15674 is a low-severity missing authorization vulnerability in Unknown Passster, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Passster WordPress plugin before 4.3.7 does not restrict low-privilege users holding the edit_posts capability from reading globally password-protected content through the WordPress core REST API when global protection is enabled, allowing any Contributor or higher to read the content of protected pages and posts without knowing the password.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-15674 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15674 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-15674 is a low-severity missing authorization vulnerability in Unknown Passster, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-15674 exists.

Affected product: Unknown Passster. 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-15674/ (Markdown: https://insights.sbomify.com/CVE-2025-15674/index.md)
```

## Sources

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

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