CVE-2026-85679 Extendify <= 3.1.6 - Unauthenticated Stored Cross-Site Scripting via 'styles.blocks' Block Type Key
Unauthenticated attackers can inject arbitrary scripts via the styles.blocks key, leading to stored XSS execution when users visit affected pages.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-85679?
CVE-2026-85679 is a high-severity cross-site scripting vulnerability in Extendify, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official 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.
Weakness: CWE-79
Which versions are affected by CVE-2026-85679?
How do I fix CVE-2026-85679?
No fix has been published for CVE-2026-85679 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-85679 being exploited?
There is no known exploitation of CVE-2026-85679 in the wild and no public exploit code.
Sources
Also known as GHSA-xx9f-33qf-3g5j.