# CVE-2026-12434: Missing authorization in List category posts

> Authenticated contributors can expose sensitive post data via shortcode, requiring plugin upgrade to fix.

- **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:** 16 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-w939-c8qp-6hm2

## What is CVE-2026-12434?

CVE-2026-12434 is a medium-severity missing authorization vulnerability in fernandobt List category posts, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The List category posts plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 0.95.0 via the sanitize_status. This makes it possible for authenticated attackers, with contributor-level access and above, to extract titles, full content, excerpts, dates, authors, and custom-field metadata of other users' pending-review, scheduled, and trashed posts by embedding a crafted [catlist] shortcode in their own draft and previewing it. This vulnerability is a bypass of the incomplete fix introduced for CVE-2025-11377 in version 0.93.0.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-12434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12434 is a medium-severity missing authorization vulnerability in fernandobt List category posts, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12434 in the wild and no public exploit code.

Affected product: fernandobt List category posts. 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-12434/ (Markdown: https://insights.sbomify.com/CVE-2026-12434/index.md)
```

## Sources

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

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