Strategic Overview
- Status
- Patched in 1.5.52
- Affected Plugin
- SpiderCalendar
- Affected Version
<= 1.5.51- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2017-7719
At a glance
CVE-2017-7719 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the SpiderCalendar WordPress plugin, affecting versions <= 1.5.51. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.5.52; sites on affected versions should update now. Disclosed April 2017, reported by Manuel Garcia Cardenas.
Vulnerability Overview
SQL injection in the Spider Event Calendar (aka spider-event-calendar) plugin before 1.5.52 for WordPress is exploitable with the order_by parameter to calendar_functions.php or widget_Theme_functions.php, related to front_end/frontend_functions.php.
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 privileges on the target site, 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 SpiderCalendar <= 1.5.51 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 SpiderCalendar the fix is 1.5.52: builds <= 1.5.51 are affected, anything from 1.5.52 onward is not.
Remediation
Update to version 1.5.52, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to SpiderCalendar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: SpiderCalendar 1.5.52 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in SpiderCalendar
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C