CVE-2026-109150

WP PageNavi Style <= 1.4 - Stored XSS via CSRF

  • High 7.1
  • A public exploit reference is listed

Description

The WP PageNavi Style WordPress plugin through 1.4 does not sanitise and escape some of its settings, and has no CSRF check when they are saved, which could allow attackers to make a logged-in administrator store arbitrary JavaScript via a CSRF attack that is then executed in the browser of everyone who visits the site's front end.

Key facts

Published
5 Nov 2026
Last changed
6 Nov 2026
Assigned by
WPScan
EPSS
0.09% likely to be exploited in the next 30 days, higher than 0.433% of CVEs (scores for 16 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.1CVSS 3.1, Highfrom CISA (ADP container)CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
UnknownWP PageNavi Style
  • Default status: unknown
  • 0 up to and including 1.4 (affected)

Timeline

  1. 5 Nov 2026 Published

Weakness

Practice this bug class

HackZoneLabs has a hands-on lab on XSS (stored, reflected, DOM) (CWE-79).

References