CVE-2014-9096 json
Multiple SQL injection vulnerabilities in recover.php in Pligg CMS 2.0.1 and earlier allow remote attackers to execute arbitrary SQL comman…
published 11y ago modified 4mo ago also EUVD-2014-8922
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in recover.php in Pligg CMS 2.0.1 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) id or (2) n parameter.
Patch / fix
Is CVE-2014-9096 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-34168)
- Published
Exploit prediction
2.40% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34168 Pligg CMS 2.0.1 - Multiple Vulnerabilities webapps, 2014-07-25
- packetstormsecurity.com http://packetstormsecurity.com/files/127615/Pligg-2.0.1-SQL-Injection-Command-Execution.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Jul/136 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 /Pligg/pligg-cms/commit/efb967b944375cd3ea3cd84c80d86d339dbe030e
- github.com /Pligg/pligg-cms/commit/4891c4d8742b9dabd67e7250840e3434865aebed
-
packetstormsecurity.com
/files/127615/Pligg-2.0.1-SQL-Injection-Command-Execution.html
exploit
-
seclists.org
/fulldisclosure/2014/Jul/136
mailing-list, exploit
-
securityfocus.com
/bid/68893
vdb-entry
Sources
- CVE List CVE-2014-9096
- NVD CVE-2014-9096
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.