Is WP Contact Form 7 DB Handler safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (3.1). As of 2026-11-04. 1 issue is on record for older versions; version 3.1 or newer fixes all of them that state a fix. Keep WP Contact Form 7 DB Handler on the latest version (3.1) and remove it if you do not use it.

Which versions of WP Contact Form 7 DB Handler are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (3.0 and older, fixed in 3.1). The full list with sources is on this page.

What is the latest version of WP Contact Form 7 DB Handler?

3.1, according to wordpress.org (last updated 2026-05-01). It has 100+ active installs.

What should I do if my WP Contact Form 7 DB Handler is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-contact-form-7-db-handler). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-contact-form-7-db-handler · data as of 2026-11-04

Is WP Contact Form 7 DB Handler safe? Known vulnerabilities and latest version

Latest version: 3.1
Last updated: 2026-05-01
Active installs: 100+
Known issues on record: 1
Unpatched in latest: 0
Tested up to WP: 6.8.12

Store all your contact form 7 submission and easily access it. you can also filter and export it! — by Yudiz Solutions Ltd.

What to do

Update to the latest version (3.1). Anything older than 3.1 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-contact-form-7-db-handler --field=version shows what you run; wp plugin update wp-contact-form-7-db-handler updates it.

Check your version

Known vulnerabilities

1 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

high 8.1 CVE-2026-6455 · published 2026-05-28

Cross-site request forgery (CSRF) in WP Contact Form 7 DB Handler (3.0 and older)

Affected: 3.0 and older
Fixed in: 3.1 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The WP Contact Form 7 DB Handler plugin for WordPress is vulnerable to Cross-Site Request Forgery leading to Arbitrary File Deletion via SQL Injection and PHP Object Injection in versions up to and including 3.0. This is due to a missing nonce verification in the process_bulk_action() function, the nonce check is only executed when _wpnonce is present in the POST body, allowing it to be trivially bypassed by omitting the field, combined with the use of an unsanitized, unparameterized user-supplied value in a numeric SQL context (WHERE ID = $ID) and the unsafe deserialization of the query result's post_content field. An attacker can craft a CSRF page that tricks a logged-in administrator into triggering a UNION-based SQL injection payload (using CHAR() to avoid esc_sql quote-escaping) that returns a malicious serialized PHP array as post_content; upon deserialization, array values associated with keys containing 'ys_cfdbh_file' are used as file paths appended to the uploads directory path without any path traversal validation, and then passed to wp_delete_file(), allowing the attacker to delete arbitrary files on the server (e.g., wp-config.php, system files).

NVD CVE-2026-6455 Wordfence advisory Code change (fix)Plugin source

Recent activity

2026-05-01 — latest release on wordpress.org (3.1).
2026-05-28 — Cross-site request forgery (CSRF) disclosed (CVE-2026-6455), fixed in 3.1.

Free. We check the CVE feeds every day and email you only when a new issue for WP Contact Form 7 DB Handler (wp-contact-form-7-db-handler) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-contact-form-7-db-handler (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-contact-form-7-db-handler"><img src="https://laskyr.com/plugins/wp-contact-form-7-db-handler/badge.svg" alt="WP Contact Form 7 DB Handler vulnerability status"></a>

← Check another plugin · Free hacked-site scan