Security readout for executives and security teams
Plain-English summary
CVE-2026-0807 affects the Frontis Blocks WordPress plugin through version 1.1.6. An unauthenticated attacker can cause the website server to make requests to arbitrary locations. This can expose limited internal data or let attackers interact with systems reachable from the web server.
Executive priority
Prioritize within the normal high-severity remediation window, faster for internet-facing WordPress sites in sensitive environments. The risk is meaningful because exploitation requires no login, but the sources do not show active exploitation or full system compromise.
Technical view
The issue is server-side request forgery in the plugin’s template_proxy function due to insufficient restriction of the url parameter. Wordfence rates it CVSS 7.2 high: network exploitable, low complexity, no privileges, no user interaction, changed scope, low confidentiality and integrity impact.
Likely exposure
Public WordPress sites running Frontis Blocks versions up to and including 1.1.6 are the likely exposure. The issue is unauthenticated and reachable over the network. The provided sources do not prove active exploitation or confirm a specific patched release version.
Exploitation context
An attacker can make outbound web requests originate from the vulnerable WordPress application through documented proxy endpoints. This may matter most where the web server can reach internal services not normally exposed to the internet. CISA KEV status is false in the provided data.
Researcher notes
Source evidence identifies CWE-918 SSRF tied to the url parameter and code references in WordPress Trac. The affected metadata in the bundle is inconsistent, while the narrative says all versions through 1.1.6. Confirm the exact fixed version from vendor or plugin repository before closure.
Mitigation direction
- Inventory WordPress sites for the Frontis Blocks plugin and version.
- Upgrade to a vendor-released version newer than 1.1.6 if available.
- If no safe update is available, disable the plugin until vendor guidance is confirmed.
- Restrict unnecessary outbound network access from WordPress servers.
- Monitor vendor, WordPress plugin, and Wordfence guidance for confirmed remediation details.
Validation and detection
- Confirm whether Frontis Blocks is installed on each WordPress site.
- Flag installed versions up to and including 1.1.6.
- Review web logs for unusual requests to template proxy or proxy image endpoints.
- Review outbound web requests from WordPress servers for unexpected internal or external destinations.
- Verify compensating egress controls limit server-side requests to approved destinations.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0807 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N3.92.7Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.2HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/322e0a27-9119-4b46-a043-d3a68c4fcdc4?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/frontis-blocks/trunk/includes/Admin/Admin.php#L910CVE reference
- https://plugins.trac.wordpress.org/browser/frontis-blocks/tags/1.1.4/includes/Admin/Admin.php#L910CVE reference
- https://plugins.trac.wordpress.org/changeset/3444616/CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.