Spider Calendar < 1.1.3 - Multiple Vulnerabilities
Strategic Overview
- Status
- Patched in 1.1.3
- Affected Plugin
- spider-calendar
- Affected Version
< 1.1.3- CVSS
- 7.2High
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the spider-calendar WordPress plugin, affecting versions < 1.1.3. 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 1.1.3; sites on affected versions should update now. Disclosed October 2012, reported by Daniel Barragan "D4NB4R".
Vulnerability Overview
The Spider Calendar plugin for WordPress is vulnerable to generic SQL Injection, Cross-Site Scripting, and Parameter Pollution via several parameters in versions up to, and including,1.1.2 due to insufficient escaping on the user supplied parameters and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database, and to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link.
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 spider-calendar < 1.1.3 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 spider-calendar the fix is 1.1.3: builds < 1.1.3 are affected, anything from 1.1.3 onward is not.
Remediation
Update to version 1.1.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to spider-calendar: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: spider-calendar 1.1.3 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