CVE-2014-9178 json
Multiple SQL injection vulnerabilities in classes/ajax.php in the Smarty Pants Plugins SP Project & Document Manager plugin (sp-client-docu…
published 2014-12-02 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9003
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.6%
- EPSS 4.6% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in classes/ajax.php in the Smarty Pants Plugins SP Project & Document Manager plugin (sp-client-document-manager) 2.4.1 and earlier for WordPress allow remote attackers to execute arbitrary SQL commands via the (1) vendor_email[] parameter in the email_vendor function or id parameter in the (2) download_project, (3) download_archive, or (4) remove_cat function.
Timeline
- First public exploit (EDB-35313)
- Published
Exploit prediction
4.63% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35313 WordPress Plugin SP Client Document Manager 2.4.1 - SQL Injection webapps, 2014-11-21
- packetstormsecurity.com http://packetstormsecurity.com/files/129212/WordPress-SP-Client-Document-Manager-2.4.1-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
exploit-db.com
/exploits/35313
exploit
-
packetstormsecurity.com
/files/129212/WordPress-SP-Client-Document-Manager-2.4.1-SQL-Injection.html
exploit
- itas.vn /news/itas-team-phat-hien-nhieu-lo-hong-sql-injection-trong-sp-client-document-manager-plugin-67.html
-
exchange.xforce.ibmcloud.com
/vulnerabilities/98897
vdb-entry
-
securityfocus.com
/archive/1/534041/100/0/threaded
mailing-list
Sources
- CVE List CVE-2014-9178
- NVD CVE-2014-9178
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.