Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-85679 Overview
The Extendify plugin for WordPress contains a stored Cross-Site Scripting (XSS) vulnerability affecting all versions up to and including 3.1.6. Unauthenticated attackers can inject arbitrary web scripts through the styles.blocks Block Type Key due to insufficient input sanitization and output escaping. The injected scripts execute whenever any user visits an affected page. The flaw is tracked under [CWE-79] and reported through Wordfence Vulnerability Report #38024680.
Critical Impact
Unauthenticated attackers can store malicious JavaScript via /wp/v2/global-styles REST routes, enabling session hijacking, credential theft, and site defacement across all visitors.
Affected Products
- Extendify plugin for WordPress — all versions through 3.1.6
- WordPress sites exposing the /wp/v2/global-styles REST route
- Fixed in Extendify version 3.2.0
Discovery Timeline
- 2026-10-01 - CVE-2026-85679 published to NVD
- 2026-10-03 - Last updated in NVD database
Technical Details for CVE-2026-85679
Vulnerability Analysis
The Extendify plugin registers a registerIncoming() callback that processes incoming block style variation data. The callback stores the styles.blocks Block Type Key without sanitizing script-bearing input or escaping it during later output. Any script injected into this field executes in the browser of every user who loads a page rendering the stored styles.
The stored XSS persists in the WordPress database and runs with the privileges of the viewing user. Administrators who view an affected page can have their session tokens exfiltrated, leading to full site takeover. Public visitors can be redirected to attacker-controlled infrastructure or served drive-by payloads.
Root Cause
The root cause is a REST request lifecycle flaw combined with missing output escaping. The registerIncoming() function is hooked onto rest_request_before_callbacks, which fires before WordPress evaluates the route's permission_callback. As a result, the vulnerable code path executes regardless of whether the request would ultimately be authorized. The handler then persists attacker-controlled values from styles.blocks without applying wp_kses or equivalent sanitization. See BlockStyleVariations.php line 29 and line 62 for the vulnerable logic.
Attack Vector
An unauthenticated attacker sends a crafted POST, PUT, or PATCH request to any /wp/v2/global-styles route on the target site. The request body includes a styles.blocks object whose Block Type Key contains JavaScript payload characters. Because registerIncoming() runs before permission checks, the payload is accepted and stored. The payload later renders unescaped on pages that display global styles, triggering script execution in every visitor's browser.
No verified exploit code is published. See the
[Wordfence advisory](https://www.wordfence.com/threat-intel/vulnerabilities/id/38024680-2d99-4af0-b805-6fd718a1d338?source=cve)
and [plugin hook registration at bootstrap.php line 112](https://plugins.trac.wordpress.org/browser/extendify/tags/3.1.6/bootstrap.php#L112)
for the technical details of the vulnerable code path.
Detection Methods for CVE-2026-85679
Indicators of Compromise
- Unauthenticated POST, PUT, or PATCH requests to /wp-json/wp/v2/global-styles or /wp-json/wp/v2/global-styles/<id> from unexpected sources
- Database entries in wp_posts or wp_postmeta for global styles containing <script>, onerror=, javascript:, or encoded script fragments inside styles.blocks keys
- Outbound browser requests from site visitors to unfamiliar domains after loading pages that render global styles
- Access log entries showing requests to /wp/v2/global-styles routes without preceding authentication cookies or nonces
Detection Strategies
- Inspect stored global style records for non-alphanumeric characters in Block Type Keys, which should normally match the pattern namespace/block-name
- Deploy a web application firewall (WAF) rule to flag REST writes to /wp/v2/global-styles lacking a valid X-WP-Nonce or authentication header
- Review Extendify plugin version across the estate and alert on any instance at or below 3.1.6
Monitoring Recommendations
- Enable WordPress REST API request logging and forward it to a central analytics or SIEM platform
- Monitor for sudden spikes in rest_request_before_callbacks executions tied to the global-styles namespace
- Alert on administrative session anomalies such as new cookies issued from unfamiliar IP ranges shortly after global-styles traffic
How to Mitigate CVE-2026-85679
Immediate Actions Required
- Upgrade the Extendify plugin to version 3.2.0 or later on every WordPress site in the estate
- Audit the wp_posts and wp_postmeta tables for global style entries containing script-like payloads and remove them
- Rotate administrator passwords and invalidate active WordPress sessions if evidence of exploitation exists
- Review user accounts for unauthorized administrator additions created after exposure to version 3.1.6
Patch Information
The vendor released a fix in Extendify 3.2.0. The patch is tracked in WordPress Changeset 3688833 with a full diff between 3.1.6 and 3.2.0. The update adds sanitization of block type keys and tightens the REST request handling path.
Workarounds
- Deactivate the Extendify plugin until the 3.2.0 upgrade is applied
- Restrict /wp/v2/global-styles endpoints at the WAF or reverse-proxy layer to authenticated administrator source IPs
- Disable public access to the WordPress REST API for unauthenticated users where feasible
# Example WAF rule (ModSecurity) to block unauthenticated writes to global-styles
SecRule REQUEST_URI "@rx /wp-json/wp/v2/global-styles" \
"id:1026085679,phase:1,deny,status:403,\
chain,msg:'Block unauthenticated Extendify global-styles write (CVE-2026-85679)'"
SecRule REQUEST_METHOD "@rx ^(POST|PUT|PATCH)$" \
"chain"
SecRule &REQUEST_HEADERS:X-WP-Nonce "@eq 0"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

