CVE-2023-49167

Database for CF7 <= 1.2.4 - Missing Authorization via wpcf7db_delete AJAX action

2023-11-29 00:00
R3N0

Strategic Overview

Status
Patched in 1.2.5
Affected Plugin
Database for CF7
Affected Version
<= 1.2.4
CVSS
6.5Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-49167
View all Database for CF7 vulnerabilities

At a glance

CVE-2023-49167 is a medium-severity Missing Authorization vulnerability in the Database for CF7 WordPress plugin, affecting versions <= 1.2.4. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.2.5; sites on affected versions should update now. Disclosed November 2023, reported by R3N0.

Vulnerability Overview

The Database for CF7 plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the wpcf7db_delete AJAX function in versions up to, and including, 1.2.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete CF7 Database entries.

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. A successful exploit has high impact on availability.

CWE-862: Missing Authorization

Reaching this weakness in Database for CF7 <= 1.2.4 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Database for CF7 the fix is 1.2.5: builds <= 1.2.4 are affected, anything from 1.2.5 onward is not.

Remediation

Update to version 1.2.5, 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: Database for CF7 1.2.5 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