CVE-2026-12408: Slim SEO Plugin Private Content Disclosure Vulnerability

Technical summary

CVE-2026-12408 is an Unauthorized Private Content Disclosure vulnerability in the Slim SEO WordPress plugin (versions up to 4.9.8). The vulnerability exists in the `/wp-json/slim-seo/meta-tags/ai` REST API endpoint, which is called by the `generate` function. The endpoint's `permission_callback` performs only a top-level `edit_posts` capability check without verifying read access to the specific post identified by the `object.ID` parameter. This allows the user-supplied post ID to be passed directly to `Data::get_post_content()`, which calls WordPress's `get_post()` function without regard to post status, ownership, or visibility settings. As a result, authenticated attackers with Contributor-level permissions (or higher) can retrieve and receive AI-generated summaries of the raw post content of arbitrary posts—including private posts, drafts, pending reviews, scheduled content, and password-protected posts—regardless of whether they have authorization to view the original content.

Business impact

This vulnerability enables information disclosure within your WordPress deployment. Contributors or editors with modest permissions can discover confidential content authored by others before publication, including draft articles, private posts, and password-protected material. For organizations using private posts to store sensitive business data, client information, or unpublished strategic content, this represents a material confidentiality breach. The risk is heightened in multi-author environments where access control and content confidentiality are critical—such as news organizations, agencies, and enterprise content management systems. The fact that the vulnerability requires only authenticated access (not administrative) means the attack surface includes any user with contributor-level permissions or above.

Affected systems

The Slim SEO plugin for WordPress in all versions up to and including 4.9.8 is affected. The vulnerability requires an authenticated user account with at least Contributor-level capabilities on the affected WordPress installation. If Slim SEO is not installed or has been updated beyond version 4.9.8, your WordPress site is not at risk from this specific flaw.

Exploitability

Exploitation requires authentication and is straightforward to perform. An attacker with a valid Contributor account (or higher) can craft a simple HTTP request to the `/wp-json/slim-seo/meta-tags/ai` REST API endpoint with the post ID of any post they wish to exfiltrate. The plugin will process the request and return an AI-generated summary that discloses the content. No advanced techniques, user interaction, or complex conditions are required. The low complexity and lack of any user interaction requirement make this vulnerability practical to exploit at scale against vulnerable WordPress installations.

Remediation

Update the Slim SEO plugin to a patched version that properly validates read access to the specific post before processing the request. Verify against the official Slim SEO plugin repository or the vendor's security advisory for the specific patch version. As a temporary mitigation, consider restricting REST API access or disabling the `/wp-json/slim-seo/meta-tags/ai` endpoint using a Web Application Firewall or WordPress security plugin until a patch is deployed. Additionally, review your WordPress user roles and revoke unnecessary Contributor-level permissions from accounts that do not require them.

Patch guidance

Obtain and deploy the latest version of the Slim SEO plugin from the official WordPress plugin repository. The plugin should be updated automatically by your WordPress installation if auto-updates are enabled, or manually via the Plugins dashboard. Verify the installed version matches the patched release noted in the vendor's security advisory. Test the update in a staging environment before deploying to production to ensure compatibility with your other plugins and themes.

Detection guidance

Monitor access logs and REST API request logs for unusual requests to the `/wp-json/slim-seo/meta-tags/ai` endpoint, particularly those containing post IDs for private, draft, or password-protected posts. Examine the activity of Contributor-level accounts to identify whether suspicious post IDs are being requested. WordPress security plugins and logging tools can be configured to flag REST API calls to this endpoint. If you have verbose logging enabled, review the audit trail for calls to `Data::get_post_content()` or the Slim SEO AI generation function with unexpected post parameters.

Why prioritize this

Although this vulnerability is rated CVSS 4.3 MEDIUM, it should be prioritized for prompt remediation in multi-author or content-heavy WordPress environments where post confidentiality is essential. The vulnerability requires only authenticated access at the contributor level, making it accessible to a broad class of users. In organizations with strict content access policies, the risk of information disclosure outweighs the moderate CVSS score. Prioritize patching if your WordPress deployment hosts sensitive, unpublished content or if you grant contributor access to external or untrusted parties.

Risk score, explained

The CVSS 3.1 score of 4.3 (MEDIUM) reflects the following factors: (1) Network-based attack vector requiring no special network configuration; (2) Low attack complexity—no special conditions or techniques required; (3) Low privilege requirement—only Contributor-level access needed; (4) No user interaction required; (5) Confidentiality impact is present (disclosure of post content), but integrity and availability are unaffected. The score does not account for the organizational sensitivity of unpublished or private content, which may warrant higher prioritization in specific business contexts. Organizations should assess risk based on the sensitivity of their private and draft content, not CVSS score alone.

Frequently asked questions