CVE-2026-120413 in SEO Plugin
Summary
by MITRE • 11/22/2026
The Yoast SEO WordPress plugin before 28.9 does not check that content is publicly viewable before returning its SEO metadata through a public REST endpoint, allowing unauthenticated users who know or can guess the URL of a private post, page or custom post type item to read its title, author, publication date and an excerpt of its content.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/22/2026
The vulnerability identified in Yoast SEO versions prior to 28.9 represents a significant information disclosure flaw rooted in insufficient access control mechanisms within the plugin's REST API implementation. This issue specifically affects how the plugin handles requests for Search Engine Optimization metadata, which are exposed through public-facing endpoints designed to assist search engines and other external services in indexing website content. The core technical failure lies in the absence of proper permission checks before retrieving and returning sensitive post data. When a request is made to these REST endpoints, the application logic fails to verify whether the requested resource is intended for public consumption or if it resides within a restricted area of the WordPress site that requires authentication. This oversight allows any actor with network connectivity to the server to query specific resources without providing valid credentials, provided they can determine the unique identifier or URL structure associated with those private items.
From an operational perspective, this vulnerability enables unauthenticated attackers to harvest sensitive metadata from content that administrators have explicitly marked as private, password-protected, or restricted to certain user roles. The data exposed includes critical identifiers such as post titles, author names, publication dates, and excerpts of the actual content body. While this does not constitute a direct code execution or full database compromise, it facilitates reconnaissance activities by revealing internal structures, potential administrative usernames through author fields, and snippets of proprietary or confidential information that were never intended for public dissemination. Attackers can leverage this data to map out the site's architecture, identify high-value targets based on publication dates or content themes, and potentially use the extracted excerpts as context for more sophisticated social engineering attacks against identified authors or administrators.
This flaw aligns with CWE-200, which categorizes information exposure vulnerabilities where sensitive information is accessible without proper authorization. Furthermore, in the context of the MITRE ATT&CK framework, this behavior corresponds to techniques under the Discovery tactic, specifically T1592 Gather Victim Host Information and potentially T1486 Data Localized Impact if the exposed content leads to further exploitation steps. The lack of validation against post status or capability checks violates fundamental security principles regarding least privilege and secure default configurations for RESTful interfaces in Content Management Systems like WordPress.
To mitigate this risk, site administrators must upgrade Yoast SEO to version 28.9 or later immediately, as the vendor has released patches that enforce strict permission verification before serving metadata through public endpoints. Until an update is applied, temporary mitigations include restricting access to the REST API via web application firewall rules if feasible, although this may impact legitimate functionality. Additionally, ensuring that all private content does not rely solely on visibility settings without complementary security layers can reduce exposure. Regular auditing of plugin configurations and keeping third-party extensions updated are essential practices for maintaining the integrity and confidentiality of WordPress-based environments against such information leakage vulnerabilities.