CVE-2021-24360

Yes/No Chart < 1.0.12 - Authenticated SQL Injection

2021-05-31 00:00
apple502j

Strategic Overview

Status
Patched in 1.0.12
Affected Plugin
Yes/No Chart
Affected Version
< 1.0.12
CVSS
6.5Medium
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24360
View all Yes/No Chart vulnerabilities

At a glance

CVE-2021-24360 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Yes/No Chart WordPress plugin, affecting versions < 1.0.12. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account. The issue is fixed in version 1.0.12; sites on affected versions should update now. Disclosed May 2021, reported by apple502j.

Vulnerability Overview

The Yes/No Chart WordPress plugin before 1.0.12 did not sanitise its sid shortcode parameter before using it in a SQL statement, allowing medium privilege users (contributor+) to perform Blind SQL Injection attacks.

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.

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

Reaching this weakness in Yes/No Chart < 1.0.12 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 Yes/No Chart the fix is 1.0.12: builds < 1.0.12 are affected, anything from 1.0.12 onward is not.

Remediation

Update to version 1.0.12, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

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