WordPress Plugin Proxy Validation Bypass Enables SSRF and XSS

The Stape Conversion Tracking WordPress plugin before 2.3.11 does not validate the sub-path appended to its same-origin proxy's upstream endpoint, allowing unauthenticated visitors to redirect the server-side request to an arbitrary host and have the response body and its content type returned from the site's own origin with security response headers stripped, leading to Server-Side Request Forgery, including loopback and internal hosts, and Cross-Site Scripting.

Casky was already ahead

This CVE exploits attack patterns that Casky's 331matched 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 Stape Conversion Tracking WordPress plugin versions before 2.3.11 contain a critical Server-Side Request Forgery (SSRF) vulnerability in their same-origin proxy mechanism. By failing to validate the sub-path parameter appended to the upstream endpoint, attackers can redirect server-side requests to arbitrary hosts—including internal infrastructure and loopback addresses—while returning responses through the legitimate site's origin with security headers stripped. This transforms the vulnerable WordPress installation into a pivot point for reconnaissance and exploitation of internal systems. Any website running the affected plugin version is exposed, with no authentication required, making this particularly dangerous for organizations using Stape's conversion tracking across their WordPress infrastructure.

Casky's 331 matched security skills leverage Claude AI with extended reasoning to detect the attack patterns underlying this vulnerability across both TA0001 (Reconnaissance) and TA0006 (Credential Access) tactics. Practitioners using Casky would identify suspicious findings including: unauthenticated requests to the proxy endpoint with unusual sub-path parameters, outbound connections to unexpected internal IP ranges or loopback addresses (127.0.0.1, 169.254.x.x), HTTP responses returning content from non-Stape origins, and security header anomalies (missing X-Frame-Options, Content-Security-Policy stripping). The platform's skills correlate these signals to flag SSRF probing attempts and subsequent XSS payload injection via response manipulation, enabling teams to detect both reconnaissance phases and active exploitation before internal systems are compromised.

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 →

331 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-118422.

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 TA0006

Investigate the attack patterns behind CVE-2026-118422

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

Run the skill that detects this →

X Instagram LinkedIn