WordPress Plugin Stored XSS via Unsanitized Visitor Tracking Data

The WP Visitor Statistics (Real Time Traffic) WordPress plugin before 8.8 does not sanitize and escape tracking data derived from public visitor requests before storing it and outputting it in the administrative statistics dashboard, allowing unauthenticated attackers to inject arbitrary web scripts that execute when a logged-in administrator views the statistics pages.

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

This vulnerability is a stored Cross-Site Scripting (XSS) flaw in the WP Visitor Statistics plugin that fails to sanitize visitor tracking data before storage and display. Unauthenticated attackers can inject malicious JavaScript through normal visitor requests, which then executes in the administrator dashboard when logged-in admins view statistics pages. This is particularly dangerous because it bypasses authentication—the attacker never needs credentials—yet compromises administrators who do have them. Any WordPress site running versions before 8.8 of this plugin is vulnerable, making this a widespread risk across the WordPress ecosystem. The CVSS 8.8 rating reflects the high impact: attackers gain admin-level execution context and can steal sessions, modify site content, or deploy further attacks.

Casky's 323 mapped skills detect this attack pattern by correlating MITRE techniques TA0001 (Initial Access—unauthenticated request injection) and TA0043 (Reconnaissance—data gathering from public endpoints) with input validation and output encoding deficiencies. Practitioners using Casky would see findings flagging the absence of input sanitization on tracking parameters, the lack of contextual output escaping in administrative templates, and the stored nature of the payload—creating a persistence vector. Claude's extended reasoning identifies the attack chain: an attacker crafts a malicious HTTP referrer or user-agent, the plugin stores it unsanitized in the database, and rendering to administrators triggers execution. This skill coverage enables teams to detect similar patterns across their WordPress deployments and prioritize remediation of plugins handling user-influenced data without proper HTML entity encoding or Content Security Policy enforcement.

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-117571.

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-117571

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

Run the skill that detects this →

X Instagram LinkedIn