CVE-2026-24991

Extensions For CF7 <= 3.4.0 - Authenticated (Contributor+) Insecure Direct Object Reference

2026-01-23 00:00
Nabil Irawan

Strategic Overview

Status
Patched in 3.4.1
Affected Version
<= 3.4.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-24991
View all Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) vulnerabilities

At a glance

CVE-2026-24991 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) WordPress plugin, affecting versions <= 3.4.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.4.1; sites on affected versions should update now. Disclosed January 2026, reported by Nabil Irawan.

Vulnerability Overview

The Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.4.0 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Contributor-level access and above, to perform an unauthorized action.

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

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) <= 3.4.0 takes an account at Contributor level or above. 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 Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) the fix is 3.4.1: builds <= 3.4.0 are affected, anything from 3.4.1 onward is not.

Remediation

Update to version 3.4.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Extensions For CF7 (Contact form 7 Database, Conditional Fields and Redirection) 3.4.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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