Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister and publish bbPress forum topic
-
DeliverySet malicious author display name
-
ExploitPayload stored in GA4/Matomo tracking script
-
ExecutionVictim loads public authored page
-
ImpactScript executes in victim browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires two specific preconditions: (1) the site must have the 'Track Authors' custom dimension configured in the plugin's Google Analytics 4 or Matomo settings - a non-default analytics configuration, and (2) the attacker must be able to publish public singular content (e.g., create a bbPress forum topic) so their author display name is rendered inside the generated tracking script. The author display name field is the exact injection point, which is neither sanitized on input nor escaped on output. Limiting factors: if 'Track Authors' is not enabled, the payload is never rendered; and the attacker needs an account/capability to publish public content with a controllable display name, so despite the PR:N in the published CVSS vector, real exploitation is gated by content-publishing access plus a specific opt-in plugin setting. |
| Impact | This is a stored XSS (CWE-79) in the SEOPress WordPress plugin rated CVSS 7.2 with vector AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, reported by Wordfence. The CVSS vector claims unauthenticated (PR:N), low-complexity, network exploitation - but this conflicts materially with the description, which states the attacker 'must be able to publish public singular content (e.g., via bbPress forum topics)' and that the 'Track Authors' custom dimension must first be configured in GA4 or Matomo. These are real preconditions: an account capable of publishing content and a non-default analytics configuration, which realistically argue for PR:L and AC:H rather than PR:N/AC:L - verify authentication requirement with vendor. No EPSS score, KEV listing, or confirmed POC was provided in the input, so there is no signal of active or probable exploitation; this is 'no public exploit identified at time of analysis.' The scope-change (S:C) correctly reflects that injected script executes in other site visitors' browsers. Net assessment: a legitimate but conditional vulnerability whose real-world risk is lower than the 7.2 headline suggests because exploitation depends on a specific analytics feature being enabled plus content-publishing access, not a blanket unauthenticated internet-facing attack. |
| Exploit ScenarioDerived | On a SEOPress site that has enabled the 'Track Authors' custom dimension in its Google Analytics 4 or Matomo settings, an attacker who can publish public content (for example by registering and creating a bbPress forum topic) sets their author display name to a malicious script payload. When any visitor loads a public singular page authored by the attacker, the display name is rendered unescaped inside the analytics tracking script and the script executes in the visitor's browser. No public exploit code was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 03, 2026
Stored cross-site scripting in the SEOPress - AI SEO Plugin & On-site SEO for WordPress (all versions up to and including 10.2) lets an attacker inject arbitrary JavaScript that is rendered unescaped inside the plugin's Google Analytics 4 or Matomo tracking script. Two preconditions gate real exploitation: the non-default 'Track Authors' custom dimension must be configured in the plugin's GA4/Matomo settings, and the attacker must be able to publish public singular content (for example a bbPress forum topic) so their controllable author display name reaches the tracking output. Wordfence reports it as CVSS 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N); no public exploit identified at time of analysis, and our own independent assessment rates it lower at AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N because the opt-in analytics setting plus content-publishing access make exploitation conditional rather than trivial.
RemediationAI
Upstream fix available (PR/commit); released patched version not independently confirmed - the vendor reference points to a WordPress.org Trac changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3722789%40wp-seopress&new=3722789%40wp-seopress), so administrators should update to the latest SEOPress release newer than 10.2 available on WordPress.org and verify the author display name is sanitized before it reaches the GA4/Matomo tracking output. Until a patched release is confirmed applied, the highest-value compensating control is to turn off the 'Track Authors' custom dimension in the plugin's Google Analytics 4 and Matomo settings, which prevents the vulnerable code path from rendering the display name at all - the trade-off is loss of author-level analytics attribution in GA4/Matomo reports. Because exploitation also requires the ability to publish public singular content (e.g., bbPress topics), restrict publishing capabilities to trusted roles, disable bbPress topic creation for untrusted registrations, or force display names to be validated/sanitized via a WordPress name filter; these reduce the attack surface but do not fix the underlying missing output escaping. Additionally, a Content Security Policy that disallows inline script execution can blunt the payload, though it may break legitimate inline analytics snippets, and sites should monitor for anomalous scripts in analytics tracking output. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/8f5f5b75-abaf-4e4b-8509-f8b569519166?source=cve for updated patch guidance.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
This is a persistent (stored) cross-site scripting flaw, CWE-79, in the WordPress plugin tracked as CPE cpe:2.3:a:rainbowgeek:seopress_-_ai_seo_plugin_&_on-site_seo and catalogued by ENISA as EUVD-2026-91905. The plugin emits front-end analytics code for Google Analytics 4 and Matomo; when the 'Track Authors' custom dimension is enabled, it interpolates the content author's WordPress display name directly into the generated tracking script. The author display name field is neither sanitized on input nor escaped on output, which the referenced source shows at inc/functions/options-google-analytics.php (approximately line 635) and inc/functions/options-matomo.php (approximately line 118) of plugin tag 10.2. Because the malicious payload is persisted in the display name and later rendered into a page on every view of the affected singular content, it executes in the browser of any visitor - including privileged users - in the context of the site origin. The assessed vector AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N reflects a scope change (script runs in the analytics/page context) combined with high attack complexity and low impact: the attacker must already hold a role capable of publishing public content and the site owner must have opted into the non-default Track Authors dimension, without which the injected value is never emitted.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Requires non-default 'Track Authors' analytics config (AC:H) and content-publishing access with a controllable display name (PR:L); stored script runs in other visitors' browsers (S:C) with limited C/I.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
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.
Executive ViewAI
The SEOPress WordPress plugin (versions up to and including 10.2) contains a high-severity stored cross-site scripting vulnerability that could allow attackers to inject malicious scripts into web pages viewed by site visitors and administrators. Exploitation requires a non-default analytics setting and content-publishing access, but if met, it could lead to session hijacking, data theft, or site defacement, damaging organizational reputation and user trust. No public exploit code has been identified at this time, and no vendor patch is available, making immediate mitigation critical.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the SEOPress plugin, disabling the 'Track Authors' custom dimension, restricting content publishing to trusted users, and deploying WAF XSS rules.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
EUVD-2026-91905
GHSA-2vm8-35r3-2p8v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB