CVE-2026-12408 json
Slim SEO <= 4.9.8 - Authenticated (Contributor+) Insufficient Authorization to Private Content Disclosure via 'object.ID' Parameter
published 2026-07-01 4 mo ago modified 2026-07-01 4 mo ago also EUVD-2026-40937
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- rilwis Slim SEO – A Fast & Automated SEO Plugin For WordPress
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/6e6603a0-8f35-49fb-a517-ba6344538c4d?source=cve
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.8/src/MetaTags/AI.php#L55
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.8/src/MetaTags/AI.php#L21
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.8/src/MetaTags/Data.php#L117
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.5/src/MetaTags/AI.php#L55
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.5/src/MetaTags/AI.php#L21
- plugins.trac.wordpress.org /browser/slim-seo/tags/4.9.5/src/MetaTags/Data.php#L117
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3576523%40slim-seo&new=3576523%40slim-seo&sfp_email=&sfph_mail=
Sources
- CVE List CVE-2026-12408
- NVD CVE-2026-12408
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.