dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-0807

HIGH · 7.2 CVSS v3.1 Published 2026-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Frontis Blocks WordPress plugin versions up to 1.1.6 contain an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in the 'template_proxy' function. Attackers can supply arbitrary URLs via the 'url' parameter through the '/template-proxy/' or '/proxy-image/' endpoints, causing the server to make requests to attacker-controlled locations.

MitigationImplement strict allowlist-based validation for the 'url' parameter to restrict requests to trusted domains only, or disable the proxy functionality if not required. Update to version 1.1.7 or later when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Frontis Blocks plugin is installed
    Check the WordPress plugin directory for the Frontis Blocks plugin folder, typically at /wp-content/plugins/frontis-blocks/ or via WP-CLI: wp plugin list --name='frontis-blocks'
    Affected if The plugin folder exists in the WordPress installation
  2. Identify installed plugin version
    Read the main plugin file header for the Version field, e.g., /wp-content/plugins/frontis-blocks/frontis-blocks.php, or use WP-CLI: wp plugin get frontis-blocks --field=version
    Affected if The version number is 1.1.6 or lower
  3. Test vulnerable endpoint accessibility
    Send a GET request to /wp-json/frontis/v1/template-proxy/?url=http://example.com (or /template-proxy/ and /proxy-image/ endpoints) and observe if the server attempts to fetch the URL
    Affected if The endpoint responds and appears to accept a url parameter without authentication
  4. Verify SSRF behavior exists
    Supply an arbitrary URL in the 'url' parameter (e.g., pointing to a controlled test server or internal IP) and check if the server makes an outbound request to that location
    Affected if The server successfully fetches and returns content from the attacker-supplied URL, confirming SSRF is possible

A defender is affected if Frontis Blocks plugin version 1.1.6 or lower is installed AND the /template-proxy/ or /proxy-image/ endpoints are accessible without authentication and accept arbitrary URLs in the url parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict allowlist-based validation for the 'url' parameter to restrict requests to trusted domains only, or disable the proxy functionality if not required. Update to version 1.1.7 or later when available.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (newer than 1.1.6)

  1. 1. Navigate to the WordPress plugin repository and check for the latest version of the Frontis Blocks plugin
  2. 2. Upgrade the Frontis Blocks plugin to the latest available version (newer than 1.1.6)
  3. 3. Verify the update was successful by checking the installed version in WordPress admin under Plugins
  4. 4. Confirm the '/template-proxy/' and '/proxy-image/' endpoints are no longer accessible or have been patched
Caveat Review plugin changelog for any breaking changes before upgrading in production environments

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0807 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0807 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data