Advanced CF7 DB <= 2.0.9 - Cross-Site Request Forgery to Form Entry Deletion
Strategic Overview
- Status
- Patched in 2.1.0
- Affected Plugin
- Advanced Contact form 7 DB
- Affected Version
<= 2.0.9- CVSS
- 5.4Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-0811
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
Other vulnerabilities in Advanced Contact form 7 DB
- 9.8CVE-2019-13571: Advanced Contact Form 7 DB <= 1.6.2 SQL Injection
CVE-2019-13571 - 8.8CVE-2021-24905: Advanced Contact form 7 DB Arbitrary File Deletion
CVE-2021-24905 - 8.5Advanced Contact form 7 DB <= 1.6.0 SQL Injection
- 7.5CVE-2024-45293: PHPSpreadsheet Library < 2.3.0 XXE Injection
CVE-2024-45293 - 6.1CVE-2022-29408: Advanced Contact form 7 DB <= 1.8.7 Stored XSS
CVE-2022-29408 - 5.3CVE-2024-4319: Advanced… Unauthenticated Information Disclosure
CVE-2024-4319 - 5.3CVE-2024-3723: Advanced Contact form 7 DB <= 2.0.2 Info Exposure
CVE-2024-3723 - 4.3CVE-2026-57669: Advanced Contact form 7 DB Missing Authorization
CVE-2026-57669
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C