CVE-2026-12408: Slim SEO (WordPress plugin) · Information Exposure
Affects Slim SEO (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 4.3 Medium.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| rilwisSlim SEO – A Fast & Automated SEO Plugin For WordPress | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict user roles to limit Contributor-level access and above to trusted users only. Monitor for updates from the plugin vendor regarding a security patch and apply it promptly once released.
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/6e6603a0-8f35-49fb-a517-ba6344538c4d?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.8/src/MetaTags/AI.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.8/src/MetaTags/AI.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.8/src/MetaTags/Data.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.5/src/MetaTags/AI.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.5/src/MetaTags/AI.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/slim-seo/tags/4.9.5/src/MetaTags/Data.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3576523%40slim-seo&new=3576523%40slim-seo&sfp_email=&sfph_mail= (opens in a new tab)