← WordPress Vulnerabilities
WordPress security by component

SEOPress

SEOPress provides tools for managing search engine optimization settings and metadata in WordPress.

SEOPress (wp-seopress) is a WordPress plugin with 8 published CVE records in this archive. The latest tracked vulnerability was published Oct 03, 2026; the highest published CVSS base score is 7.2.

Plugin slug: wp-seopress

CVE-2026-96564: SEOPress: Stored XSS through author tracking dimensions

The SEOPress – AI SEO Plugin & On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Author Display Name in all versions up to, and including, 10.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the 'Track Authors' custom dimension to be configured in the plugin's Google Analytics 4 or Matomo settings, and the attacker must be able to publish public singular content (e.g., via bbPress forum topics) so that the injected display name is rendered in the tracking script. The export calls the issue unauthenticated but also requires attacker-controlled author metadata and the ability to publish public singular content. It does not establish a universal minimum WordPress role; those publication and tracking-configuration prerequisites must both hold. No fixed release is confirmed by the reviewed evidence. Upstream version 10.3 is newer and may resolve the issue, but its changelog does not clearly confirm this specific fix.

PublishedOct 03, 2026
Safe version guidanceSee mitigation notes
Published vulnerabilities for wp-seopress
Safe version
Oct 03, 2026 CVE-2026-96564
SEOPress: Stored XSS through author tracking dimensions
The SEOPress – AI SEO Plugin & On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Author Display Name in all versions up to, and including, 10.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the 'Track Authors' custom dimension to be configured in the plugin's Google Analytics 4 or Matomo settings, and the attacker must be able to publish public singular content (e.g., via bbPress forum topics) so that the injected display name is rendered in the tracking script. The export calls the issue unauthenticated but also requires attacker-controlled author metadata and the ability to publish public singular content. It does not establish a universal minimum WordPress role; those publication and tracking-configuration prerequisites must both hold. No fixed release is confirmed by the reviewed evidence. Upstream version 10.3 is newer and may resolve the issue, but its changelog does not clearly confirm this specific fix.
See mitigation notes
CVE7.2
NVDPending
Oct 03, 2026 CVE-2026-101357
SEOPress: Stored XSS through delegated Matomo settings
The SEOPress – AI SEO Plugin & On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'seopress_google_analytics_matomo_id' parameter in all versions up to, and including, 10.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with subscriber-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This requires an administrator to have delegated the Analytics management capability to the Subscriber role via the plugin's Advanced > Security settings. No fixed release is confirmed by the reviewed evidence. Upstream version 10.3 is newer and may resolve the issue, but its changelog does not clearly confirm this specific fix.
See mitigation notes
CVE4.9
NVDPending
Sep 03, 2026 CVE-2026-85305
SEOPress permits low-privilege server-side request forgery
SEOPress through 10.1 allows a low-privilege authenticated user to influence a server-side request. The request can reach resources available to the WordPress host and may expose or alter data when a victim interacts with the affected flow.
10.2
CVE5.4
NVDPending
Oct 29, 2024 CVE-2024-50454
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVDPending
Oct 02, 2024 CVE-2024-9225
SEOPress – On-site SEO: Cross-site scripting
SEOPress – On-site SEO is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.1
NVDPending
Jun 20, 2024 CVE-2024-1168
SEOPress – On-site SEO: Cross-site scripting
SEOPress – On-site SEO is affected by cross-site scripting. Exploitation requires an authenticated contributor account. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.4
NVD5.4
May 06, 2024 CVE-2024-34383
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVDPending
Aug 16, 2021 CVE-2021-34641
SEOPress: A security weakness
SEOPress is affected by a security weakness. Exploitation requires an authenticated WordPress account. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE6.4
NVD5.4