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).
CVE-2026-6455
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-28. NVD baseline CVSS 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(medium)
- EPSS
- 16.0%
- KEV
- Not listed
Published
May 28, 2026
Last Modified
May 28, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/tags/3.0/include/form-inner-page-class.php#L589
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/tags/3.0/include/form-inner-page-class.php#L605
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/tags/3.0/include/form-inner-page-class.php#L607
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/tags/3.0/include/form-inner-page-class.php#L615
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/trunk/include/form-inner-page-class.php#L589
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/trunk/include/form-inner-page-class.php#L605
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/trunk/include/form-inner-page-class.php#L607
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-contact-form-7-db-handler/trunk/include/form-inner-page-class.php#L615
- security@wordfencehttps://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3520240%40wp-contact-form-7-db-handler&new=3520240%40wp-contact-form-7-db-handler&sfp_email=&sfph_mail=
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/96cdba03-7385-4374-915d-061be0276a95?source=cve
Vendor Advisories for CVE-2026-6455(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 79× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 168 total refreshes for this CVE.
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-13 22:31 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-13 06:13 UTCEPSS rescore
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 21:39 UTCEG score recompute
- 2026-07-11 21:39 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 22:48 UTCEG score recompute
- 2026-07-08 22:48 UTCGHSA enrichment
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 02:31 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-02 14:31 UTCEG score recompute
- 2026-07-02 14:31 UTCGHSA enrichment
- 2026-07-01 16:00 UTCEG score recompute
- 2026-07-01 16:00 UTCGHSA enrichment
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-07-01 03:25 UTCEG score recompute
- 2026-07-01 03:25 UTCGHSA enrichment
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-30 02:14 UTCEG score recompute
- 2026-06-30 02:14 UTCGHSA enrichment
- 2026-06-29 14:06 UTCEPSS rescore
- 2026-06-29 13:47 UTCEG score recompute
- 2026-06-29 13:47 UTCGHSA enrichment
- 2026-06-28 19:20 UTCEG score recompute
- 2026-06-28 19:20 UTCGHSA enrichment
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 06:45 UTCEG score recompute
- 2026-06-28 06:45 UTCGHSA enrichment
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 18:21 UTCEG score recompute
- 2026-06-27 18:21 UTCGHSA enrichment
- 2026-06-27 05:31 UTCEG score recompute
- 2026-06-27 05:31 UTCGHSA enrichment
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 16:55 UTCEG score recompute
- 2026-06-26 16:55 UTCGHSA enrichment
- 2026-06-25 23:50 UTCEG score recompute
- 2026-06-25 23:50 UTCGHSA enrichment
- 2026-06-25 13:50 UTCEPSS rescore
- 2026-06-25 11:22 UTCEG score recompute
- 2026-06-25 11:22 UTCGHSA enrichment
- 2026-06-24 22:57 UTCEG score recompute
- 2026-06-24 22:57 UTCGHSA enrichment
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 14:56 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-19 19:26 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 18:27 UTCEG score recompute
- 2026-06-17 18:27 UTCGHSA enrichment
- 2026-06-17 17:53 UTCEPSS rescore
- 2026-06-17 04:13 UTCEG score recompute
- 2026-06-17 04:13 UTCGHSA enrichment
- 2026-06-16 17:53 UTCEPSS rescore
- 2026-06-16 15:47 UTCEG score recompute
- 2026-06-16 15:47 UTCGHSA enrichment
- 2026-06-16 01:32 UTCEG score recompute
- 2026-06-16 01:31 UTCGHSA enrichment
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-15 13:08 UTCEG score recompute
- 2026-06-15 13:07 UTCGHSA enrichment
- 2026-06-15 00:11 UTCEG score recompute
- 2026-06-15 00:11 UTCGHSA enrichment
- 2026-06-14 23:18 UTCEPSS rescore
- 2026-06-14 11:47 UTCEG score recompute
- 2026-06-14 11:47 UTCGHSA enrichment
- 2026-06-13 23:23 UTCEG score recompute
- 2026-06-13 23:23 UTCGHSA enrichment
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-13 11:00 UTCEG score recompute
- 2026-06-13 11:00 UTCGHSA enrichment
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 22:34 UTCEG score recompute
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-6455?
When was CVE-2026-6455 disclosed?
Is CVE-2026-6455 actively exploited?
What is the CVSS score of CVE-2026-6455?
How do I remediate CVE-2026-6455?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6455
Is Your Infrastructure Affected by CVE-2026-6455?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.