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

CVE-2026-11395

HIGH · 7.2 CVSS v3.1 Published 2026-06-18
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 CF7 to Webhook plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.0.0 via the pull_the_trigger. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Exploitation requires that the admin-configured webhook URL contains a Contact Form 7 field placeholder in the host segment of the URL, and that the affected form is publicly accessible.

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 CF7 to Webhook WordPress plugin allows unauthenticated Server-Side Request Forgery (SSRF) via the pull_the_trigger function. When admin-configured webhook URLs contain Contact Form 7 field placeholders in the host segment, attackers can manipulate these placeholders to force the server to make requests to attacker-controlled or internal destinations.

MitigationUpdate to the latest version of the plugin if available, or remove Contact Form 7 field placeholders from the host segment of webhook URLs and implement strict allowlist-based URL validation before making outbound requests.

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. Verify CF7 to Webhook plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and search for 'CF7 to Webhook', or check the /wp-content/plugins/ directory for a cf7-to-webhook folder
    Affected if Plugin is present in the WordPress installation
  2. Determine installed plugin version
    Read the version from the plugin header in the main PHP file (typically cf7-to-webhook.php) or view it in the WordPress plugins list
    Affected if Version is older than the patched version (compare against latest version on WordPress repository)
  3. Inspect webhook URL configurations
    Navigate to the plugin settings in WordPress admin (usually under Contact Form 7 > Webhook or a dedicated CF7 Webhook settings page) and examine all configured webhook URL fields
    Affected if Any webhook URL contains Contact Form 7 field placeholders (e.g., [field_name]) in the host portion of the URL (scheme://[placeholder]/path)
  4. Check if webhook functionality is active
    Look for any active webhook configurations or published forms that have webhook endpoints enabled in the plugin settings
    Affected if Webhook URLs are saved and active in the plugin configuration

If the CF7 to Webhook plugin is installed with any webhook URLs configured that contain CF7 field placeholders in the host segment, the environment is vulnerable to unauthenticated SSRF attacks via the pull_the_trigger function

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

Update to the latest version of the plugin if available, or remove Contact Form 7 field placeholders from the host segment of webhook URLs and implement strict allowlist-based URL validation before making outbound requests.

Recommended fix Moderate confidence

Upgrade to a version greater than 5.0.0 (e.g., 5.0.1 or latest available)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate the 'CF7 to Webhook' plugin
  4. Check if the current version is 5.0.0 or below
  5. If vulnerable, click 'Update Now' if an update is available, or download the latest version from the WordPress plugin repository and upload it manually
  6. After updating, verify the plugin version is greater than 5.0.0
  7. Confirm that webhook forms using CF7 field placeholders in URL hosts are now properly protected
Caveat Review webhook configurations after upgrade to ensure functionality remains intact

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11395 — 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-11395 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