CVE-2026-85679
Received Received - Intake

Stored XSS in Extendify WordPress Plugin

Vulnerability report for CVE-2026-85679, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-01

Last updated on: 2026-10-01

Assigner: Wordfence

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-01
Last Modified
2026-10-01
Generated
2026-10-01
AI Q&A
2026-10-01
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
extendify plugin to 3.1.6 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

The Extendify plugin for WordPress has a stored Cross-Site Scripting (XSS) vulnerability due to insufficient input sanitization and output escaping in the 'styles.blocks' Block Type Key. This allows unauthenticated attackers to inject malicious scripts into pages. The vulnerability is triggered by unauthenticated POST, PUT, or PATCH requests to a /wp/v2/global-styles route because the registerIncoming() function runs before WordPress checks route permissions.

Detection Guidance

This vulnerability can be detected by checking if the Extendify plugin version 3.1.6 or lower is installed on your WordPress site. Inspect the plugin files for the presence of the 'styles.blocks' Block Type Key in the global-styles route handling. Look for unauthenticated POST, PUT, or PATCH requests to /wp/v2/global-styles endpoints.

Impact Analysis

This vulnerability allows attackers to inject arbitrary web scripts into WordPress pages. When users access an infected page, the malicious scripts execute, potentially stealing sensitive data, session cookies, or performing actions on behalf of the user. It can lead to unauthorized access, data breaches, or defacement of websites.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA by exposing user data to unauthorized access or theft. GDPR requires protecting personal data, and HIPAA mandates safeguarding protected health information. A successful exploit may result in data breaches, triggering legal penalties, fines, or reputational damage for organizations.

Mitigation Strategies

Immediately update the Extendify plugin to the latest version beyond 3.1.6. If an update is not available, consider disabling or removing the plugin until a patch is released. Review server logs for suspicious requests to /wp/v2/global-styles endpoints and block unauthorized access to these routes.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-85679. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart