ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress - Security Vulnerability (CVE-2026-108041)

Q: Am I affected by this vulnerability?

You are affected if your site runs ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress. Versions below 10.4 are vulnerable; that release and later are not.

Q: How do I fix it?

Update ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress to version 10.4 or later. That is the complete fix. Until you can update, Request / payload inspection (WAF) in Hack Halt ProSecure contains this class of attack at the request layer.

Q: What can an attacker actually do?

This is a Cross-Site Scripting (XSS) flaw. An attacker who exploits it can run script in a visitor's browser, stealing sessions or planting an administrator account.

CVE-2026-108041

Vulnerability CVE-2026-108041 PLUGIN ng-settings-before-outputting-them-in-an-inline-script-printed-on-every-front-end-page-allowing-users-granted-a-seopress HIGH

The SEOPress WordPress plugin before 10.4 does not sanitise and escape some of its analytics tracking settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress WordPress plugin before 10.4 capability that an administrator can delegate to lower-privileged roles to perform Stored Cross-Site Scripting attacks that execute in the browser of any site visitor, including a logged-in administrator viewing the front end.

CVE-2026-108041

HIGH CVSS 7.1 Published 2026-11-04 Updated 2026-11-04

AI Risk Elevated (65/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P3 Priority

Severity Band HIGH

CVSS Vector CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H

Affected Components 2

Reference Links 1

AI Risk Engine Elevated (65/100)

Exploitability Medium

Active Exploitation No strong signal

Published Exploit Status No public exploit references

Threat Timeline

2026-11-04 CVE published and first recorded in the threat feed.
2026-11-04 Record updated with latest vulnerability metadata.
2026-11-12 AI technical context refreshed for mitigation and impact guidance.
Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 17 hours ago

AI enriched 17 hours ago (2026-11-12 02:30 UTC)

Technical Summary

Potential Impact

Severity is HIGH (CVSS 7.1). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Medium based on severity and technical exposure profile.

Primary risk drivers: severity and technical exposure profile

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 65/100 (Elevated, Medium) with priority P3 Priority. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress PLUGIN · ng-settings-before-outputting-them-in-an-inline-script-printed-on-every-front-end-page-allowing-users-granted-a-seopress Affected: < 10.4 Fixed in: 10.4

SEOPress PLUGIN · seopress Affected: < 10.4 Fixed in: 10.4

References

https://wpscan.com/vulnerability/5776859a-d381-4e89-b263-4e22a74bfa83/

What to do about this

Patch on your next cycle Worth fixing, but not ahead of other work.

Fix it

Update ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress to 10.4 or later.

That is the complete fix. Everything below is what protects you in the meantime.

Cannot update today? Request / payload inspection (WAF) in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Inspect request parameters and bodies for injection, traversal and file-inclusion payloads, and refuse the request rather than logging it.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs ng settings before outputting them in an inline script printed on every front-end page, allowing users granted a SEOPress, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?