CVE-2026-120515Cross-site Scripting (XSS)
NVDCVSS scored by security@wordfence.com
Vulnerability Summary
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.
CVSS v3.1 Base Metrics — Score 6.4 (MEDIUM)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NAttack VectorNetwork
Attack ComplexityLow
Privileges RequiredLow
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone
Affected & Patched Versions
Not provided by NVD for this CVE.
No patched version published yet
Until a fix ships, reduce exposure:
- Restrict access to the affected service or interface to trusted networks.
- Disable the affected feature if you do not need it.
- Watch the vendor advisory for a firmware or software update.
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run the affected product and which version.
- No patched version is listed yet. Limit access to the affected service to trusted networks, and disable the feature if you can.
- Subscribe to the vendor advisory so you learn when a fix ships.
Timeline
- Nov 7, 2026Published
- Nov 7, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get alerts for CVEs like this oneYou are reading CVE-2026-120515. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://plugins.svn.wordpress.org/wp-seopress/trunk/
- Referencehttps://plugins.trac.wordpress.org/browser/wp-seopress/tags/10.3/inc/admin/sanitize/Sanitize.php#L63
- Referencehttps://plugins.trac.wordpress.org/browser/wp-seopress/tags/10.3/inc/functions/options-google-analytics.php#L800
- Referencehttps://plugins.trac.wordpress.org/browser/wp-seopress/tags/10.3/inc/functions/options-google-analytics.php#L822
- Referencehttps://plugins.trac.wordpress.org/browser/wp-seopress/tags/10.3/src/Actions/Api/Options/AnalyticsSettings.php#L104
- Referencehttps://plugins.trac.wordpress.org/browser/wp-seopress/tags/10.4/inc/functions/options-google-analytics.php
- Referencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/10a13871-c98e-4785-ab41-18e548e07c05?source=cve
Data last checked: Nov 7, 2026 08:01 UTC