CVE-2026-107652

Database Addon for Contact Form 7 <= 1.4.1 - Unauthenticated Limited File Deletion via Injected 'attackcfdb7_file' Submission Field

2026-10-13 12:38
Sawyer

Strategic Overview

Status
Patched in 1.4.2
Affected Plugin
Database Addon for Contact Form 7 – CFDB7
Affected Version
<= 1.4.1
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-107652
View all Database Addon for Contact Form 7 – CFDB7 vulnerabilities

At a glance

CVE-2026-107652 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Database Addon for Contact Form 7 WordPress plugin, affecting versions <= 1.4.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.4.2; sites on affected versions should update now. Disclosed October 2026, reported by Sawyer.

Vulnerability Overview

The Database Addon for Contact Form 7 – CFDB7 plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to, and including, 1.4.1. This is due to the plugin storing arbitrary (non-form-tag) submission fields in its db7_forms row and the process_bulk_action() delete handler then matching any stored key whose name contains the substring 'cfdb7_file' and passing the stored value directly to unlink() without validating that the file actually belongs to the submission being deleted or constraining the filename with basename()/realpath(). This makes it possible for unauthenticated attackers to inject a crafted multipart field.

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, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Database Addon for Contact Form 7 <= 1.4.1 carries this weakness at cfdb7_file, and reaching it takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Database Addon for Contact Form 7 the fix is 1.4.2: builds <= 1.4.1 are affected, anything from 1.4.2 onward is not.

Remediation

Update to version 1.4.2, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Database Addon for Contact Form 7 1.4.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-107652https://www.wordfence.com/threat-intel/vulnerabilities/id/7de3606a-254c-4e5f-9499-b1cc79dce7c8https://nvd.nist.gov/vuln/detail/CVE-2026-107652

Related records

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