WordPress Extendify Plugin Stored XSS in Block Styles

The Extendify plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'styles.blocks' Block Type Key in all versions up to, and including, 3.1.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This is possible because registerIncoming() is hooked on rest_request_before_callbacks and runs before WordPress evaluates the route's permission_callback, meaning any unauthenticated POST, PUT, or PATCH request to a /wp/v2/global-styles route can trigger the vulnerable code path.

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 Extendify plugin for WordPress contains a Stored Cross-Site Scripting (XSS) vulnerability affecting all versions up to 3.1.6. Attackers can inject malicious JavaScript through the 'styles.blocks' block type key due to insufficient input sanitization and output escaping. Because the vulnerable registerIncoming() function hooks into rest_request_before_callbacks—executing before WordPress applies its standard security checks—unauthenticated attackers can embed arbitrary scripts that persist in the database and execute whenever any user views the infected page. This vulnerability threatens all WordPress installations using the affected Extendify versions, impacting site administrators, content editors, and end users who may unknowingly execute attacker-controlled code in their browsers.

Casky's 323 matched skills leverage Claude AI with extended reasoning to detect this attack pattern by mapping to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify detection patterns including: REST API endpoint abuse indicating early exploitation attempts (TA0001), suspicious block configuration payloads containing script tags in style parameters, timing anomalies showing requests bypassing standard WordPress sanitization hooks, and stored payload signatures persisting across page renders. The platform's security skills would highlight the critical indicator—REST requests hitting the registerIncoming() handler with encoded or obfuscated JavaScript in block styling parameters—allowing teams to correlate these findings with compromised page content and user access logs to scope breach impact and initiate rapid remediation.

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

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

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

Run the skill that detects this →

X Instagram LinkedIn