EUVD-2026-40937
GHSA-h4h4-h3cx-x6xc
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
PR:L confirmed by required Contributor account; C:L because disclosure is via AI summaries, not verbatim raw content; no integrity or availability impact applies.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Unauthorized private content disclosure in the Slim SEO WordPress plugin (all versions through 4.9.8) allows authenticated Contributors to read protected content they do not own via the /wp-json/slim-seo/meta-tags/ai REST API endpoint. The endpoint's broken object-level authorization - checking only the generic edit_posts capability rather than per-post read access - lets any Contributor supply an arbitrary post ID and receive an AI-generated summary of that post's raw content, including private, draft, pending, future, and password-protected posts authored by other users. No public exploit or CISA KEV listing is identified at time of analysis; real-world risk is constrained by the requirement for a pre-existing Contributor-level account.
Technical ContextAI
This is a CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) rooted in broken object-level authorization, a pattern closely related to OWASP API Security Top 10 API1. The vulnerable REST endpoint /wp-json/slim-seo/meta-tags/ai implements a permission_callback that validates only the generic edit_posts WordPress capability - granted to Contributors and above - without performing any per-object authorization check against the post ID supplied by the caller. The attack path, confirmed via WordPress plugin Trac source references, flows from AI.php (lines 21 and 55 in the tagged 4.9.8 release) into Data::get_post_content() in Data.php (line 117), which calls WordPress core's get_post() unconditionally regardless of post status or ownership. This means any post in any status (private, draft, pending, scheduled, password-protected) is reachable. The affected product is identified by CPE cpe:2.3:a:rilwis:slim_seo_-_a_fast_&_automated_seo_plugin_for_wordpress:*:*:*:*:*:*:*:*.
RemediationAI
Update the Slim SEO plugin via the WordPress plugin dashboard or the official WordPress plugin repository to any version released after 4.9.8, where the fix changeset (https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3576523%40slim-seo&new=3576523%40slim-seo) is incorporated. The exact patched release version number is not independently confirmed in the available data - verify the installed version against the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/6e6603a0-8f35-49fb-a517-ba6344538c4d after updating. Where immediate patching is not possible, site administrators can block REST API access to the /wp-json/slim-seo/meta-tags/ai endpoint using a WAF rule or a WordPress REST API filtering plugin such as Disable REST API, noting that this will disable the plugin's AI summary generation feature. Additionally, auditing and removing unnecessary Contributor-level accounts reduces the exploitable attack surface. Restricting WordPress user registration (Settings > General > uncheck 'Anyone can register') prevents attackers from self-provisioning qualifying accounts.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Same weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today