# CVE-2026-109150: WP PageNavi Style <= 1.4 - Stored XSS via CSRF

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Unknown / WP PageNavi Style: ≥ 0; ≤ 1.4 (affected, semver). Source: CNA: WPScan

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-79, CWE-352

## Exploit evidence

- exploit: https://wpscan.com/vulnerability/10a889d8-9e15-42b9-a001-622e97ab5d06/ (CNA: WPScan)

## References

- https://wpscan.com/vulnerability/10a889d8-9e15-42b9-a001-622e97ab5d06/ (CNA: WPScan; exploit, vdb-entry, technical-description)

## Provenance

- CNA: WPScan: https://www.cve.org/CVERecord?id=CVE-2026-109150; retrieved 2026-11-05; source updated 2026-11-05

Revision: 48b9b4cc421ab8f2ce8933eb7f4ae69012f362f1bec19a91084d44b0a6122ae3

Canonical: https://y2.dev/cve/CVE-2026-109150

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.