CVE-2026-85679 extendify CVE debrief

Who should care

Defenders responsible for WordPress installations using the Extendify plugin should assess exposure and prioritize verification of unauthenticated POST, PUT, or PATCH requests to /wp/v2/global-styles routes.

Why it matters

CVE-2026-85679 allows unauthenticated attackers to inject arbitrary web scripts in WordPress pages using the Extendify plugin. Defenders should verify exposure, prioritize remediation, and monitor for suspicious activity.

• Unauthenticated attackers can inject arbitrary web scripts
• Scripts execute when a user accesses an injected page
• Verify exposure of WordPress installations using the Extendify plugin
• Prioritize remediation of vulnerable versions

Technical summary

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. The vulnerability is caused by the registerIncoming() function being hooked on rest_request_before_callbacks, which runs before WordPress evaluates the route's permission_callback, allowing unauthenticated attackers to inject arbitrary web scripts.

Defensive priority

Defenders should prioritize verifying exposure of WordPress installations using the Extendify plugin, especially those allowing unauthenticated POST, PUT, or PATCH requests to /wp/v2/global-styles routes.

Recommended defensive actions

• Verify exposure of WordPress installations using the Extendify plugin
• Check for unauthenticated POST, PUT, or PATCH requests to /wp/v2/global-styles routes
• Escalate to administrators if vulnerable versions are found
• Apply vendor remediation when available
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability allows 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.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.