CVE-2026-0807
Server-Side Request Forgery in Frontis Blocks WordPress Plugin
Publication date: 2026-01-24
Last updated on: 2026-01-24
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| unknown_vendor | frontis_blocks | to 1.1.6 (inc) |
| unknown_vendor | frontis_blocks | 1.1.7 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-918 | The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The vulnerability in the Frontis Blocks WordPress plugin (up to version 1.1.6) is a Server-Side Request Forgery (SSRF). It occurs because the 'url' parameter in the 'template_proxy' function is not properly restricted. This allows unauthenticated attackers to make the web application send requests to arbitrary locations via the '/template-proxy/' and '/proxy-image/' endpoints, potentially abusing the server to access internal or external resources.
How can this vulnerability impact me? :
This SSRF vulnerability can allow attackers to make the server perform unintended web requests, which could lead to information disclosure (such as accessing internal network resources), bypassing firewalls, or interacting with internal services that are not normally accessible externally. It can also be used as a stepping stone for further attacks, potentially compromising confidentiality and integrity of data.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring or scanning for HTTP requests made to the vulnerable endpoints '/template-proxy/' and '/proxy-image/' that include the 'url' parameter. Since the vulnerability allows unauthenticated attackers to make arbitrary web requests via these endpoints, you can detect exploitation attempts by searching web server logs or network traffic for requests to these paths with suspicious or external URLs in the 'url' parameter. For example, using command-line tools on the server hosting the WordPress site, you can run commands like: 1. To search Apache or Nginx access logs for requests to the vulnerable endpoints: grep -E "/template-proxy/|/proxy-image/" /var/log/apache2/access.log 2. To filter requests that include the 'url' parameter: grep -E "/template-proxy/|/proxy-image/" /var/log/apache2/access.log | grep "url=" 3. Using tcpdump to capture HTTP traffic and filter for these endpoints: sudo tcpdump -A -s 0 'tcp port 80 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)' | grep -E "/template-proxy/|/proxy-image/" These commands help identify potential exploitation attempts by detecting requests targeting the vulnerable plugin endpoints with the 'url' parameter. Further analysis of the URLs requested can help confirm malicious activity.
What immediate steps should I take to mitigate this vulnerability?
The immediate mitigation step is to update the Frontis Blocks WordPress plugin to version 1.1.7 or later, as this version includes a comprehensive fix for the vulnerability CVE-2026-0807. The update addresses all security issues by introducing sanitization, validation, and other security hardening measures across the plugin's components. If updating immediately is not possible, consider temporarily disabling the plugin or restricting access to the vulnerable endpoints '/template-proxy/' and '/proxy-image/' via web server configuration or firewall rules to prevent exploitation. Monitoring and blocking suspicious requests targeting these endpoints can also help reduce risk until the update is applied. [4]