CVE-2014-9528 json
SQL injection vulnerability in the actionIndex function in protected/modules_core/notification/controllers/ListController.php in HumHub 0.1…
published 2015-01-06 11 y ago modified 2026-06-17 4 mo ago also EUVD-2014-9342
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in the actionIndex function in protected/modules_core/notification/controllers/ListController.php in HumHub 0.10.0-rc.1 and earlier allows remote authenticated users to execute arbitrary SQL commands via the from parameter to index.php. NOTE: this can be leveraged for cross-site scripting (XSS) attacks via a request that causes an error.
Patch / fix
Timeline
- First public exploit (EDB-35510)
- Published
Exploit prediction
2.34% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35510 Humhub 0.10.0-rc.1 - SQL Injection webapps, 2014-12-10
- packetstormsecurity.com http://packetstormsecurity.com/files/129440/Humhub-0.10.0-rc.1-Cross-Site-Scripting-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Dec/31 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
References
- github.com /humhub/humhub/commit/febb89ab823d0bd6246c6cf460addabb6d7a01d4
-
exploit-db.com
/exploits/35510
exploit
-
packetstormsecurity.com
/files/129440/Humhub-0.10.0-rc.1-Cross-Site-Scripting-SQL-Injection.html
exploit
-
seclists.org
/fulldisclosure/2014/Dec/31
mailing-list, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/99272
vdb-entry
Sources
- CVE List CVE-2014-9528
- NVD CVE-2014-9528
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.