CVE-2016-7400 json
Multiple SQL injection vulnerabilities in Exponent CMS before 2.4.0 allow remote attackers to execute arbitrary SQL commands via the (1) id…
published 2017-02-07 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-8256
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Exponent CMS before 2.4.0 allow remote attackers to execute arbitrary SQL commands via the (1) id parameter in an activate_address address controller action, (2) title parameter in a show blog controller action, or (3) content_id parameter in a showComments expComment controller action.
Patch / fix
Timeline
- First public exploit (EDB-40412)
- Published
Exploit prediction
4.65% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-40412 Exponent CMS 2.3.9 - Blind SQL Injection webapps, 2016-09-22
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| 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
/exponentcms/exponent-cms/commit/e916702a91a6342bbab483a2be2ba2f11dca3aa3
issue-tracking, patch, third-party-advisory
-
exponentcms.lighthouseapp.com
/projects/61783/changesets/e916702a91a6342bbab483a2be2ba2f11dca3aa3
patch, vendor-advisory
-
exploit-db.com
/exploits/40412/
exploit
- github.com /exponentcms/exponent-cms/releases/tag/v2.4.0
-
openwall.com
/lists/oss-security/2016/09/18/2
mailing-list, third-party-advisory
-
openwall.com
/lists/oss-security/2016/09/18/10
mailing-list, third-party-advisory
-
securityfocus.com
/bid/93041
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-7400
- NVD CVE-2016-7400
Fencer Vulns 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.