WordPress PageNavi Plugin XSS via CSRF in Settings

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.

Casky was already ahead

This CVE exploits attack patterns that Casky's 323matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The WP PageNavi Style plugin through version 1.4 contains a critical vulnerability that combines two attack vectors: missing CSRF protection and insufficient output sanitization in plugin settings. An attacker can craft a malicious webpage that, when visited by a logged-in administrator, silently submits a request to store arbitrary JavaScript in the plugin's settings without the admin's knowledge or consent. Once stored, this malicious script executes in the browsers of all site visitors, turning the compromised WordPress site into a vector for credential theft, malware distribution, or website defacement. This affects any WordPress installation using this plugin with administrative users who may visit untrusted sites while logged in.

Casky's 323 matching skills leverage Claude's extended reasoning to detect the attack chain across MITRE ATT&CK's Initial Access (TA0001) and Persistence (TA0043) tactics. Practitioners using Casky would identify suspicious patterns such as: unexpected JavaScript injection in database settings, anomalous admin requests lacking CSRF tokens, and cross-origin POST requests to wp-admin endpoints modifying plugin configurations. The platform would surface CWE-79 (Stored XSS) indicators through behavioral analysis of administrator activity logs, flag requests to vulnerable plugin endpoints, and correlate CSRF absence with settings modifications. Security teams would receive findings highlighting the specific attack flow—from initial social engineering that lures admins to malicious sites, through CSRF exploitation, to persistent JavaScript execution affecting all site visitors—enabling rapid detection and remediation before widespread compromise.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

323 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-109150.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-109150

Casky has 323 skills that investigate the attack patterns behind CVE-2026-109150. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn