Yoast SEO vulnerability records and the roles their titles name
Read this Yoast SEO history by the access wording in each title, which includes Contributor+, Author+ and Seo Manager+, and by each record's version fields.
The checks cover head output, the sitemap, schema blocks and the accounts with Editor capabilities, on a site you are authorised to review.
On this page
Yoast SEO vulnerability history
Source: Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . It lists 20 records for Yoast SEO. Copyright notices, licence terms and a link to each source record are under Data source and licence at the foot of this page.
Update to at least version 28.1
Worked out from data retrieved on .
Every affected range listed in this source for Yoast SEO ends before version 28.1.
A vendor can publish a security release before this source records it. Read the plugin's own changelog as well as this history.
Yoast SEO <= 28.0 - Authenticated (Author+) Stored Cross-Site Scripting via Post Slug (post_name)
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-15425
Affected versions- All versions up to and including 28.0
Patched versions: 28.1
Update to at least version 28.1.
Yoast SEO <= 26.5 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposure via 'post_id' Parameter
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.3)
- CVE:
- CVE-2025-14481
Affected versions- All versions up to and including 26.5
Patched versions: 26.6
Update to at least version 26.6.
Yoast SEO <= 27.1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'jsonText' Block Attribute
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-3427
Affected versions- All versions up to and including 27.1.1
Patched versions: 27.2
Update to at least version 27.2.
Yoast SEO <= 26.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'yoast-schema' Block Attribute
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2026-1293
Affected versions- All versions up to and including 26.8
Patched versions: 26.9
Update to at least version 26.9.
Yoast SEO <= 22.6 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2024-4984
Affected versions- All versions up to and including 22.6
Patched versions: 22.7
Update to at least version 22.7.
Show 15 older recordsHide the older records
Yoast SEO <= 22.5 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2024-4041
Affected versions- All versions up to and including 22.5
Patched versions: 22.6
Update to at least version 22.6.
Yoast SEO <= 21.0 - Authenticated (Seo Manager+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.5)
- CVE:
- CVE-2023-40680
Affected versions- All versions up to and including 21.0
Patched versions: 21.1
Update to at least version 21.1.
Yoast SEO <= 20.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
Affected versions- All versions up to and including 20.2
Patched versions: 20.2.1
Update to at least version 20.2.1.
Yoast SEO <= 17.2 - Full Path Disclosure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
- CVE:
- CVE-2021-25118
Affected versions- All versions before 17.3
Patched versions: 17.3
Update to at least version 17.3.
Yoast SEO <= 11.5 - Authenticated Stored Cross Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.4)
- CVE:
- CVE-2019-13478
Affected versions- All versions up to and including 11.5
Patched versions: 11.6-RC5
Update to at least version 11.6-RC5.
Yoast SEO <= 9.1.0 - Race Condition to Remote Code Execution
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.6)
- CVE:
- CVE-2018-19370
Affected versions- All versions up to and including 9.1.0
Patched versions: 9.2.0
Update to at least version 9.2.0.
Yoast SEO <= 5.7.1 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2017-16842
Affected versions- All versions up to and including 5.7.1
Patched versions: 5.8.0
Update to at least version 5.8.0.
Yoast SEO <= 3.4.0 - Authenticated Stored Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.4)
- CVE:
- CVE-2021-24153
Affected versions- All versions before 3.4.1
Patched versions: 3.4.1
Update to at least version 3.4.1.
Yoast SEO <= 3.2.5 - Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 4.7)
Affected versions- All versions up to and including 3.2.5
Patched versions: 3.3.0
Update to at least version 3.3.0.
Yoast SEO <= 3.2.4 - Sensitive Data Exposure
- Published:
- Last updated:
- Severity:
- Medium (CVSS 5.3)
Affected versions- All versions up to and including 3.2.4
Patched versions: 3.2.5
Update to at least version 3.2.5.
Yoast SEO <= 2.0.1 - Reflected Cross-Site Scripting
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
Affected versions- All versions before 2.1
Patched versions: 2.1
Update to at least version 2.1.
Yoast SEO <= 1.7.3.3 - Blind SQL Injection
- Published:
- Last updated:
- Severity:
- High (CVSS 8.8)
- CVE:
- CVE-2015-2292
Affected versions- All versions up to and including 1.5.6
- From version 1.6 up to and including 1.6.3
- From version 1.7 up to and including 1.7.3
Patched versions: 1.5.7, 1.6.4, 1.7.4
Update to at least the patched version for your release line: 1.5.7, 1.6.4, 1.7.4.
Yoast SEO <= 1.7.3.3 - Cross-Site Request Forgery
- Published:
- Last updated:
- Severity:
- High (CVSS 7.5)
- CVE:
- CVE-2015-2293
Affected versions- All versions up to and including 1.5.6
- From version 1.6 up to and including 1.6.3
- From version 1.7 up to and including 1.7.3.3
Patched versions: 1.5.7, 1.6.4, 1.7.4
Update to at least the patched version for your release line: 1.5.7, 1.6.4, 1.7.4.
Yoast SEO <= 1.4.6 - Missing Authorization
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.5)
Affected versions- All versions up to and including 1.4.6
Patched versions: 1.4.7
Update to at least version 1.4.7.
Yoast SEO <= 2.1.1 - Cross Site Scripting via post_title parameter
- Published:
- Last updated:
- Severity:
- Medium (CVSS 6.1)
- CVE:
- CVE-2012-6692
Affected versions- All versions up to and including 2.1.1
Patched versions: 2.2
Update to at least version 2.2.
Check Yoast SEO on a live site
Read-only checks for a site you own or are authorised to review. Each step uses the WordPress dashboard or WP-CLI and sends no test payloads to the site.
Yoast SEO inputs: post fields, blocks, tools and abilities
Yoast SEO is the free plugin at the WordPress.org address ending in wordpress-seo, the slug the checklist on this page uses.
Its listing names titles, meta descriptions and focus keyphrases, which it says a free bulk editor can review and fix across the whole site, HowTo and FAQ blocks with built-in schema support, and import and export tools for SEO data and settings.
Titles in this history name roles. WordPress documents a Contributor as able to write its own posts but not publish them, and an Author as able to publish its own. Yoast's developer documentation lists two roles the plugin adds, wpseo_editor and wpseo_manager, and says both inherit all capabilities of the Editor role.
A Yoast developer page also describes two abilities that other software can call to read and update a post's SEO data.
Yoast SEO vulnerabilities on record: roles and release lines
An ending that recurs is Authenticated (Contributor+) Stored Cross-Site Scripting.
It stands alone on CVE-2024-4984 (all versions up to and including 22.6, patched in 22.7), and on CVE-2026-1293 it continues via 'yoast-schema' Block Attribute (up to and including 26.8, patched in 26.9). CVE-2026-15425 has a title ending Authenticated (Author+) Stored Cross-Site Scripting via Post Slug (post_name) (up to and including 28.0, patched in 28.1), and CVE-2023-40680 has a title ending Authenticated (Seo Manager+) Stored Cross-Site Scripting (up to and including 21.0, patched in 21.1).
Some things in the fields complicate a match.
- Three release lines. CVE-2015-2292, whose title ends Blind SQL Injection, and CVE-2015-2293, whose title ends Cross-Site Request Forgery, each list three affected ranges and three patched versions: 1.5.7, 1.6.4 and 1.7.4. Use the range for the line installed.
- Title against fields. Both of those titles say 1.7.3.3. The last range on CVE-2015-2293 ends at 1.7.3.3, while on CVE-2015-2292 it ends at 1.7.3. For that record the fields say nothing about the versions between 1.7.3 and 1.7.4, so the patched version is the one to reach.
- No CVE id. The record whose title ends Authenticated (Contributor+) Stored Cross-Site Scripting and whose affected range ends at 20.2 (patched in 20.2.1) has none, so a search by CVE id will miss it.
A second place to read
Before relying on the update guidance at the top of the history, also read the changelog Yoast publishes for each release: the records here are what the source data held when it was last imported, not a list of everything the vendor has fixed.
Yoast SEO security checks: settings, page source and public addresses
Some of these checks end at a toggle in the Yoast SEO settings.
Record its state and do not slide it.
On the Plugins screen the Description column includes each plugin's version number. Write down the Yoast SEO version, and separately that of any paid Yoast plugin; the records in the history are those filed under the free plugin's slug. Yoast documents a filter in Yoast SEO Premium for hiding the version number in the HTML source code. Take the number from the dashboard, not from page source.
In the source of the home page and one post, copy the head. The tags Yoast's Metadata API page lists include the title, meta description, canonical link and robots tag, and the tags of its webmaster presenters, for Baidu, Bing, Google, Pinterest and Yandex. Ask who owns the account behind each one you find.
Note any canonical or robots tag you did not expect: the plugin's help text says the advanced section of its meta box lets a user remove a post from the search results or change the canonical.
Yoast also documents a GET request to /wp-json/yoast/v1/get_head?url= followed by a page address, calls the API read-only for now, and says it can be disabled in the Site features section of the Yoast SEO Settings menu. Request one public page while logged out and note whether it answers.
Yoast's help article puts an XML sitemaps toggle in Yoast SEO, then Settings, then Site features, under Technical SEO. Write down whether it is on. A developer page says enabling the feature serves the index at /sitemap_index.xml and replaces the WordPress core sitemaps, while a warning in the plugin's help text says disabling Yoast SEO's XML sitemaps will not disable WordPress' core sitemaps. With the toggle off, check whether WordPress serves its own.
Open the index and each sitemap it lists. The functional specification says authors, meaning users with at least one published, public, indexable post, should get a sitemap when the content type is public and has valid members, and WordPress notes that an author's username is often included in the URL of their author archive.
List the accounts an author sitemap reveals, and any address you expected to be private: the specification says private or password-protected pages should be excluded.
Yoast's developer documentation says an FAQ block adds the FAQPage type to a page's WebPage schema piece and a HowTo block adds a HowTo piece. Some titles in this history end with a Block Attribute phrase. As this page's own check, list the posts that use a Yoast block and who wrote them; a developer page names two, yoast/faq-block and yoast/how-to-block.
Yoast's developer pages also describe a Schema aggregation endpoint that is disabled by default in Yoast SEO and, when enabled, serves the site's public structured data as a schema map at /schemamap.xml. The plugin's listing marks Schema aggregation for NLWeb as Premium. Request that address and record whether it is served.
On the Users screen, use the Role column to write down every Editor and every account in the two Yoast roles, which Yoast says inherit all capabilities of the Editor role. WordPress documents that an Editor on a single site holds unfiltered_html, which it says allows posting HTML markup or even JavaScript code, and Yoast's security program page lists users with administrator or editor privileges posting arbitrary JavaScript as out of scope. So count either Yoast role as an Editor when you list who holds that trust.
Then look for a toggle about advanced or schema settings for authors, which the plugin's help text names Security: no advanced or schema settings for authors, and record its state. That help text says that by default only editors and administrators can use the advanced section and the schema tab of the Yoast SEO meta box, and that Off allows all users to change those settings.
Ask whoever maintains the theme whether any code uses the filters Yoast documents for changing which roles hold its capabilities.
What a Yoast SEO version number leaves out
Some questions about a Yoast SEO site sit outside every version field: which accounts hold wpseo_manager or wpseo_editor, whether the authors toggle is Off, whether theme code has widened a Yoast capability through its roles filter, and what the head endpoint returns to a logged-out visitor.
An installed version inside one of the affected ranges in the history shows that a known record covers that release, and says nothing on whether the flaw was used on your site.
A WordPress security audit starts logged out: it lists the REST routes under /wp-json/, where Yoast documents its get_head address, and calls each one without a session. It also records who holds the Editor role, whose capabilities Yoast says its two roles inherit, and checks the screens that SEO plugins add for editors.
Frequently asked questions
Each record carries its own affected range and patched versions field, and some carry more than one range: CVE-2015-2293 lists three, the last ending at 1.7.3.3. Compare every part of your installed version with each range, then read the update guidance at the top of the history.
The plugin's listing says Yoast SEO is updated every two weeks. A site updated only every few months can be several releases behind, so read the installed version on the Plugins screen and set it against the update guidance at the top of the history. Since WordPress 5.5 an administrator can opt in to automatic updates plugin by plugin.
The records here are those the source data files under the slug wordpress-seo, the free plugin on WordPress.org. Being filed there does not settle whether a record also applies to Yoast SEO Premium. Yoast's security program page lists Yoast SEO (free) and Yoast SEO Premium (paid) as separate entries, and Yoast's developer site links to a separate changelog for Premium. On a site that runs both, write down both version numbers.
Yoast's developer documentation lists two default roles, wpseo_editor and wpseo_manager. The capabilities it lists for wpseo_manager include wpseo_manage_options, which it says allows access to the Yoast SEO settings pages. CVE-2023-40680 has a title ending Authenticated (Seo Manager+) Stored Cross-Site Scripting, and the title says no more about that role. On the Users screen, look for role filter links beyond the WordPress defaults.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.
Data source and licenceHide the data source and licence
The vulnerability records on this page come from Wordfence Intelligence (Vulnerability Data Feed v3, Production), retrieved on . The records contain material that is subject to copyright. Each copyright notice and its licence are reproduced once below, followed by a link to every source record.
Copyright 2012-2026 Defiant Inc.
Applies to every record listed below.
Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.
Copyright 1999-2026 The MITRE Corporation
Applies to 15 of the 20 records listed below.
CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.
Source records
- Yoast SEO <= 28.0 - Authenticated (Author+) Stored Cross-Site Scripting via Post Slug (post_name) (CVE-2026-15425)
- Yoast SEO <= 26.5 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposure via 'post_id' Parameter (CVE-2025-14481)
- Yoast SEO <= 27.1.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'jsonText' Block Attribute (CVE-2026-3427)
- Yoast SEO <= 26.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'yoast-schema' Block Attribute (CVE-2026-1293)
- Yoast SEO <= 22.6 - Authenticated (Contributor+) Stored Cross-Site Scripting (CVE-2024-4984)
- Yoast SEO <= 22.5 - Reflected Cross-Site Scripting (CVE-2024-4041)
- Yoast SEO <= 21.0 - Authenticated (Seo Manager+) Stored Cross-Site Scripting (CVE-2023-40680)
- Yoast SEO <= 20.2 - Authenticated (Contributor+) Stored Cross-Site Scripting
- Yoast SEO <= 17.2 - Full Path Disclosure (CVE-2021-25118)
- Yoast SEO <= 11.5 - Authenticated Stored Cross Site Scripting (CVE-2019-13478)
- Yoast SEO <= 9.1.0 - Race Condition to Remote Code Execution (CVE-2018-19370)
- Yoast SEO <= 5.7.1 - Reflected Cross-Site Scripting (CVE-2017-16842)
- Yoast SEO <= 3.4.0 - Authenticated Stored Cross-Site Scripting (CVE-2021-24153)
- Yoast SEO <= 3.2.5 - Cross-Site Scripting
- Yoast SEO <= 3.2.4 - Sensitive Data Exposure
- Yoast SEO <= 2.0.1 - Reflected Cross-Site Scripting
- Yoast SEO <= 1.7.3.3 - Blind SQL Injection (CVE-2015-2292)
- Yoast SEO <= 1.7.3.3 - Cross-Site Request Forgery (CVE-2015-2293)
- Yoast SEO <= 1.4.6 - Missing Authorization
- Yoast SEO <= 2.1.1 - Cross Site Scripting via post_title parameter (CVE-2012-6692)