Frontis Blocks <= 1.1.6 - Unauthenticated Server-Side Request Forgery via 'url' Parameter
Strategic Overview
- Status
- Patched in 1.1.7
- Affected Plugin
- Frontis Blocks — Block Library for the Block Editor
- Affected Version
<= 1.1.6- CVSS
- 7.2High
- Weakness type
- CWE-918 · Server-Side Request Forgery (SSRF)
- CVE
CVE-2026-0807
At a glance
CVE-2026-0807 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in the Frontis Blocks WordPress plugin, affecting versions <= 1.1.6. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.1.7; sites on affected versions should update now. Disclosed January 2026, reported by Itthidej Aramsri (Boeing777).
Vulnerability Overview
The Frontis Blocks plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.1.6. This is due to insufficient restriction on the 'url' parameter in the 'template_proxy' function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application via the '/template-proxy/' and '/proxy-image/' endpoint.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-918: Server-Side Request Forgery (SSRF)
Frontis Blocks <= 1.1.6 carries this weakness at url, and reaching it takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.
The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For Frontis Blocks the fix is 1.1.7: builds <= 1.1.6 are affected, anything from 1.1.7 onward is not.
Remediation
Update to version 1.1.7, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Frontis Blocks 1.1.7 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C