CVE-2026-108041VulnerabilityPublished 4 Nov 2026

The SEOPress WordPress plugin before 10.4 does not sanitise and escape some of its analytics tracking settings before

Source GCVE Database

Compare

Authoritative record:CVE-2026-108041· High

Not known to be exploited : upgrade to 10.4 soon.

Data as of 4 Nov 2026, 07:43 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.

ghsa-pp67-6fqf-q73f

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

If you cannot patch yet, administrators should carefully control which users are granted SEOPress plugin capabilities that can be delegated, limiting them to trusted roles only.

Description

The SEOPress WordPress plugin versions prior to 10.4 contain a vulnerability where certain analytics tracking settings are not properly sanitized or escaped before being output in an inline script on front-end pages. This flaw allows users with a specific SEOPress capability, which can be delegated by an administrator to lower-privileged roles, to perform stored cross-site scripting (XSS) attacks. These attacks execute in the browsers of any site visitor, including logged-in administrators viewing the front end.

Impact

Successful exploitation allows attackers with delegated SEOPress plugin capabilities to inject persistent malicious scripts that execute in the browsers of any site visitor, including administrators. This can lead to session hijacking, privilege escalation, or other malicious actions executed in the context of the affected site users' browsers.

Summary

The SEOPress WordPress plugin before version 10.4 fails to sanitize and escape some analytics tracking settings before embedding them in inline scripts on every front-end page. This improper handling enables users granted a SEOPress-specific capability—delegable by administrators to less privileged roles—to inject malicious scripts that persist and execute in the browsers of site visitors and administrators. The vulnerability is a stored cross-site scripting (XSS) flaw affecting versions prior to 10.4.

References

Community reviews

Loading reviews…