CVE-2022-0254

Zero Spam <= 5.2.10 - Admin+ SQL Injection

2022-02-18 00:00
ZhongFu Su

Strategic Overview

Status
Patched in 5.2.11
Affected Version
<= 5.2.10
CVSS
7.2High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2022-0254
View all Zero Spam for WordPress vulnerabilities

At a glance

CVE-2022-0254 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Zero Spam for WordPress WordPress plugin, affecting versions <= 5.2.10. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 5.2.11; sites on affected versions should update now. Disclosed February 2022, reported by ZhongFu Su.

Vulnerability Overview

The WordPress Zero Spam WordPress plugin before 5.2.11 does not properly sanitise and escape the order and orderby parameters before using them in a SQL statement in the admin dashboard, leading to a SQL injection

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 Zero Spam for WordPress <= 5.2.10 takes a caller who can reach the endpoint. 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 Zero Spam for WordPress the fix is 5.2.11: builds <= 5.2.10 are affected, anything from 5.2.11 onward is not.

Remediation

Update to version 5.2.11, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Zero Spam for WordPress: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Zero Spam for WordPress 5.2.11 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