CVE-2021-24125

Contact Form Submissions <= 1.7 - Authenticated SQL Injection

2021-01-03 00:00
vigov5 SunCSR

Strategic Overview

Status
Patched in 1.7.1
Affected Version
<= 1.7
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24125
View all Contact Form Submissions vulnerabilities

At a glance

CVE-2021-24125 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Contact Form Submissions WordPress plugin, affecting versions <= 1.7. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account. The issue is fixed in version 1.7.1; sites on affected versions should update now. Disclosed January 2021, reported by vigov5 SunCSR.

Vulnerability Overview

Unvalidated input in the Contact Form Submissions WordPress plugin before 1.7.1, could lead to SQL injection in the wpcf7_contact_form GET parameter when submitting a filter request as a high privilege user (admin+)

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 confidentiality, integrity, availability — full site compromise territory.

CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Reaching this weakness in Contact Form Submissions <= 1.7 takes any authenticated account. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.

A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Contact Form Submissions the fix is 1.7.1: builds <= 1.7 are affected, anything from 1.7.1 onward is not.

Remediation

Update to version 1.7.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Contact Form Submissions: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Contact Form Submissions 1.7.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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