CVE-2014-5140 json
The bindReplace function in the query factory in includes/classes/database.php in Loaded Commerce 7 does not properly handle : (colon) char…
published 2020-01-03 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-5038
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
The bindReplace function in the query factory in includes/classes/database.php in Loaded Commerce 7 does not properly handle : (colon) characters, which allows remote authenticated users to conduct SQL injection attacks via the First name and Last name fields in the address book.
Patch / fix
Timeline
- First public exploit (EDB-34552)
- Published
Exploit prediction
2.68% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34552 LoadedCommerce7 - Systemic Query Factory webapps, 2014-09-07
- packetstormsecurity.com http://packetstormsecurity.com/files/128183/Loaded-Commerce-7-Shopping-Cart-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/loadedcommerce/loaded7/pull/520
patch, third-party-advisory
-
resources.infosecinstitute.com
/exploiting-systemic-query-vulnerabilities-attempt-re-invent-pdo/
patch, third-party-advisory
-
packetstormsecurity.com
/files/128183/Loaded-Commerce-7-Shopping-Cart-SQL-Injection.html
exploit, third-party-advisory, vdb-entry
-
exploit-db.com
/exploits/34552
exploit, third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95791
third-party-advisory, vdb-entry
Sources
- CVE List CVE-2014-5140
- NVD CVE-2014-5140
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.