CVE-2026-0811

Advanced CF7 DB <= 2.0.9 - Cross-Site Request Forgery to Form Entry Deletion

2026-04-08 05:13
Kai Aizen

Strategic Overview

Status
Patched in 2.1.0
Affected Version
<= 2.0.9
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-0811
View all Advanced Contact form 7 DB vulnerabilities

At a glance

CVE-2026-0811 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Advanced Contact form 7 DB WordPress plugin, affecting versions <= 2.0.9. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.1.0; sites on affected versions should update now. Disclosed April 2026, reported by Kai Aizen.

Vulnerability Overview

The Advanced Contact form 7 DB plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.0.9. This is due to missing or incorrect nonce validation on the 'vsz_cf7_save_setting_callback' function. This makes it possible for unauthenticated attackers to delete form entry via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Advanced Contact form 7 DB <= 2.0.9 carries this weakness at vsz_cf7_save_setting_callback, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Advanced Contact form 7 DB the fix is 2.1.0: builds <= 2.0.9 are affected, anything from 2.1.0 onward is not.

Remediation

Update to version 2.1.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Advanced Contact form 7 DB: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced Contact form 7 DB 2.1.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C