Simple Events Calendar <= 1.4.0 - Authenticated SQL Injection
Strategic Overview
- Status
- Patched in 1.4.1
- Affected Plugin
- Simple Events Calendar
- Affected Version
<= 1.4.0- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2021-24552
At a glance
CVE-2021-24552 is a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Simple Events Calendar WordPress plugin, affecting versions <= 1.4.0. 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.4.1; sites on affected versions should update now. Disclosed July 2021, reported by Shreya Pohekar.
Vulnerability Overview
The Simple Events Calendar WordPress plugin through 1.4.0 does not sanitise, validate or escape the event_id POST parameter before using it in a SQL statement when deleting events, leading to an authenticated SQL injection issue
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 Simple Events Calendar <= 1.4.0 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 Simple Events Calendar the fix is 1.4.1: builds <= 1.4.0 are affected, anything from 1.4.1 onward is not.
Remediation
Update to version 1.4.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Simple Events Calendar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Simple Events Calendar 1.4.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C