CVE-2021-24755

myCred – Points, Rewards, Gamification, Ranks, Badges & Loyalty Plugin <= 2.2 - Subscriber+ SQL Injection

2021-11-01 00:00
bl4derunner

Strategic Overview

Status
Patched in 2.3
Affected Version
<= 2.2
CVSS
8.8High
Weakness type
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
CVE
CVE-2021-24755
View all Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program – myCred vulnerabilities

At a glance

CVE-2021-24755 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program WordPress plugin, affecting versions <= 2.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.3; sites on affected versions should update now. Disclosed November 2021, reported by bl4derunner.

Vulnerability Overview

The myCred WordPress plugin before 2.3 does not validate or escape the fields parameter before using it in a SQL statement, leading to an SQL injection exploitable by any authenticated user

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 Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program <= 2.2 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 Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program the fix is 2.3: builds <= 2.2 are affected, anything from 2.3 onward is not.

Remediation

Update to version 2.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Points Management System For Gamification, Ranks, Badges, and Loyalty Rewards Program 2.3 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