CVE-2026-120515 · Package
NO FIX YET
SEOPress, a WordPress SEO plugin, does not sanitize its affiliate and download tracking settings before writing them into the Google Analytics snippet on pages. An authenticated user with Subscriber-level access or higher can inject scripts that run in the browser of anyone who loads an affected page.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running SEOPress 10.3 or earlier where the Google Analytics tracking features are in use. Exposure requires that an administrator has delegated the SEOPress 'analytics' capability to lower-privilege accounts; sites that only let administrators edit these settings are not exposed by this flaw.
Not affected if admin-only-analytics-capability, default-config, seopress-above-10.3
Who cares self-hosted, seopress, wordpress
wp plugin get wp-seopress --field=versionNo fix yet, per the sources.
The SEOPress – AI SEO Plugin & On-site SEO plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'seopress_google_analytics_affiliate_tracking' and 'seopress_google_analytics_download_tracking' settings in versions up to, and including, 10.3. This is due to insufficient input sanitization and output escaping on these settings as they are interpolated into the inline Google Analytics tracking snippet by seopress_google_analytics_js(): the affiliate value receives no sanitization at all (it is omitted from inc/admin/sanitize/Sanitize.php) and lands inside a <script> block, while the download value is only passed through sanitize_text_field() and lands inside a JavaScript regular-expression literal that preserves parentheses, semicolons and slashes. This makes it possible for authenticated attackers, with Subscriber-level access and above (where an administrator has delegated the SEOPress 'analytics' capability under Settings > Advanced > Security — the precondition Wordfence accepted for CVE-2026-101357), to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.