# CVE-2026-12408: Missing authorization in Slim SEO – A Fast & Automated SEO Plugin For WordPress

> Authenticated contributors can read private or draft post content via an insecure REST API endpoint in the Slim SEO WordPress plugin.

- **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:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-h4h4-h3cx-x6xc

## What is CVE-2026-12408?

CVE-2026-12408 is a medium-severity missing authorization vulnerability in rilwis Slim SEO – A Fast & Automated SEO Plugin For WordPress, published on 1 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Slim SEO – A Fast & Automated SEO Plugin For WordPress plugin for WordPress is vulnerable to Unauthorized Private Content Disclosure in all versions up to, and including, 4.9.8 via the `/wp-json/slim-seo/meta-tags/ai` REST API endpoint. This is due to the endpoint's `permission_callback` performing only a top-level `edit_posts` capability check without verifying that the requesting user has read access to the specific post supplied via the `object.ID` parameter, allowing the `generate` function to pass the attacker-controlled post ID to `Data::get_post_content()`, which calls `get_post()` regardless of post status or ownership. This makes it possible for authenticated attackers with Contributor-level access and above to retrieve AI-generated summaries of the raw `post_content` of arbitrary posts they are not authorized to view — including private posts, drafts, pending, future, and password-protected content authored by other users — with the substance of the protected content disclosed via the HTTP response.

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

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


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

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

## Is CVE-2026-12408 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12408 is a medium-severity missing authorization vulnerability in rilwis Slim SEO – A Fast & Automated SEO Plugin For WordPress, published on 1 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-12408 in the wild and no public exploit code.

Affected product: rilwis Slim SEO – A Fast & Automated SEO Plugin For WordPress. 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-12408/ (Markdown: https://insights.sbomify.com/CVE-2026-12408/index.md)
```

## Sources

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

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