VulnerabilityPublished 4 Nov 2026

CVE-2026-108041: SEOPress (WordPress plugin) · Cross-site Scripting

Affects SEOPress (WordPress plugin)Source CVE Database V5

Compare

Not known to be exploited : upgrade to 10.4 soon.

Data as of 4 Nov 2026, 06:28 UTC

Severity

High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none

Patch: Available – fixed in 10.4

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SEOPress (WordPress plugin) to 10.4.

Affected software

Product	Affected	Fixed in
SEOPress	Affected <10.4	Fixed in 10.4

AI-suggested

Upgrade SEOPress to version 10.4 or later, where this vulnerability is fixed. Until then, restrict the assignment of SEOPress capabilities to trusted users only. No other vendor advisory mitigation is provided.

Description

A stored cross-site scripting (XSS) vulnerability exists in the SEOPress WordPress plugin versions before 10.4. The plugin fails to properly sanitize and escape certain analytics tracking settings before outputting them in an inline script on every front-end page. This flaw allows users with a specific SEOPress capability, which can be delegated by an administrator to lower-privileged roles, to inject malicious scripts that execute in the browsers of any site visitor, including logged-in administrators viewing the front end.

Impact

Users with a SEOPress capability granted by an administrator can perform stored XSS attacks that execute arbitrary scripts in the browsers of any site visitor, including administrators. This can lead to session hijacking, defacement, or other malicious actions executed in the context of the vulnerable site.

Summary

The SEOPress WordPress plugin prior to version 10.4 contains a stored cross-site scripting vulnerability (CWE-79) due to improper sanitization and escaping of analytics tracking settings. These settings are output in an inline script on every front-end page, enabling users with delegated SEOPress capabilities to inject malicious scripts. This vulnerability can lead to script execution in the browsers of site visitors and administrators, potentially compromising site security. The issue is fixed in SEOPress version 10.4.

CWE-79Improper Neutralization of Input During Web Page Generation (Cross-site Scripting) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #1OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Implementation · Architecture and Design
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
Architecture and Design · Implementation · Attack Surface Reduction
Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide…
OWASP Cheat Sheets
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Injection Prevention (opens in a new tab)
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.3 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
XSS Using MIME Type Mismatch (opens in a new tab)
DOM-Based XSS (opens in a new tab)
Reflected XSS (opens in a new tab)
Stored XSS (opens in a new tab)
Cross-Site Scripting (XSS) (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

wpscan.com/vulnerability/5776859a-d381-4e89-b263-4e22a74bfa83/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 06:28 UTC

WeaknessesCWE-79

Technical details

References

Community reviews

Related threats