CVE-2026-0807

High

Published: 24 January 2026

Published

24 January 2026

Modified

15 April 2026

KEV Added

—

Patch

—

CVSS Score 7.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS Score 0.0003 9.2th percentile

Risk Priority 14 60% EPSS · 20% KEV · 20% CVSS

Summary

CVE-2026-0807 is a high-severity SSRF (CWE-918) vulnerability in Wordpress (inferred from references). Its CVSS base score is 7.2 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 9.2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

Threat & Defense at a Glance

What attackers do: exploitation maps to Exploit Public-Facing Application (T1190) and 2 other techniques.

Threat & Defense Details

Likely Mitigating ControlsAI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

CA-8 Penetration Testing

addresses: CWE-918

Penetration testing attempts server-side requests to internal resources, identifying SSRF weaknesses for remediation.

SC-7 Boundary Protection

addresses: CWE-918

Outbound connections to external resources can be monitored and limited at the boundary, reducing SSRF impact.

SI-10 Information Input Validation

addresses: CWE-918

Validates server-side URLs and resource references to block SSRF attempts.

SI-4 System Monitoring

addresses: CWE-918

Detects server-side request forgery through monitoring of unexpected outbound connections.

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access

Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.

attack.mitre.org →

T1522 Cloud Instance Metadata API Credential Access

Adversaries may attempt to access the Cloud Instance Metadata API to collect credentials and other sensitive data.

attack.mitre.org →

T1046 Network Service Discovery Discovery

Adversaries may attempt to get a listing of services running on remote hosts and local network infrastructure devices, including those that may be vulnerable to remote software exploitation.

attack.mitre.org →

Why these techniques?

SSRF in public-facing WordPress plugin directly enables remote exploitation of the application (T1190); description explicitly notes use for accessing cloud metadata services (T1522) and internal network probing/service discovery (T1046).

Confidence: HIGH · MITRE ATT&CK Enterprise v18.1

NVD Description

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.

Deeper analysisAI

CVE-2026-0807 is a Server-Side Request Forgery (SSRF) vulnerability, classified under CWE-918, affecting the Frontis Blocks plugin for WordPress in all versions up to and including 1.1.6. The issue stems from insufficient restrictions on the 'url' parameter within the 'template_proxy' function, allowing requests to arbitrary locations originating from the web server via the '/template-proxy/' and '/proxy-image/' endpoints. It carries a CVSS v3.1 base score of 7.2 (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N), highlighting its high severity due to network accessibility, low complexity, and changed scope with limited confidentiality and integrity impacts.

Unauthenticated attackers can exploit this vulnerability remotely without privileges or user interaction by sending crafted requests to the affected endpoints. This enables them to force the WordPress server to initiate connections to arbitrary domains or internal resources, potentially bypassing firewalls, accessing metadata services, or probing internal networks from the trusted server context.

Advisories reference code locations in the plugin's Admin.php file at line 910 across version tags and trunk, along with WordPress plugin trac changeset 3444616, which likely addresses the issue post-1.1.6. Additional details are available via Wordfence threat intelligence.