CVE-2026-109150: WP PageNavi Style · Cross-site Scripting
Affects WP PageNavi StyleSource CVE Database V5
Not known to be exploited.
Data as of 5 Nov 2026, 06:27 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or noneExploitation evidence
Disclosed: evidence found.
CVE published 5 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 5 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| WP PageNavi Style | Affected
| Fixed in– |
AI-suggested
Users should apply strict administrative access controls and avoid visiting untrusted sites while logged in as administrators. Monitor for updates from the plugin vendor or WordPress plugin repository for an official fix. Until then, consider disabling or removing the plugin if possible to mitigate risk.
Description
The WP PageNavi Style WordPress plugin up to version 1.4 contains a vulnerability where some settings are not properly sanitized or escaped, and there is no CSRF protection when saving these settings. This flaw allows an attacker to perform a CSRF attack that causes a logged-in administrator to store arbitrary JavaScript, which is then executed in the browsers of site visitors.