# CVE-2026-17517: Content Views < 4.5.1.2 - Unauthenticated Non-Public Post Content Disclosure via Views Status Filter

> Unauthenticated attackers can read non-public post content if a view is configured to include them, due to missing authorization checks.

- **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:** 4 Sep 2026
- **Updated:** 4 Sep 2026
- **Also known as:** GHSA-99mx-5cm5-w53g

## What is CVE-2026-17517?

CVE-2026-17517 is a medium-severity missing authorization vulnerability in Unknown Content Views, published on 4 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Content Views  WordPress plugin before 4.5.1.2 does not check whether the user requesting a view is allowed to read the posts it returns, allowing unauthenticated attackers to obtain the title and content of non-public posts, such as draft, pending, private and scheduled posts, when a view has been configured to include them.

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

## Which versions are affected by CVE-2026-17517?


## How do I fix CVE-2026-17517?

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

## Is CVE-2026-17517 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17517 and fix it if it is affected.

What it is: CVE-2026-17517 is a medium-severity missing authorization vulnerability in Unknown Content Views, published on 4 Sep 2026. 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-2026-17517 in the wild and no public exploit code.

Affected product: Unknown Content Views. 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-2026-17517/ (Markdown: https://insights.sbomify.com/CVE-2026-17517/index.md)
```

## Sources

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

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