CVE-2014-2008 json
SQL injection vulnerability in confirm.php in the mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to execute arbitr…
published 2014-09-12 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2060
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in confirm.php in the mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to execute arbitrary SQL commands via the TID parameter.
Patch / fix
Timeline
- First public exploit (EDB-34586)
- Published
Exploit prediction
2.64% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-34586 Mpay24 PrestaShop Payment Module 1.5 - Multiple Vulnerabilities webapps, 2014-09-08
- packetstormsecurity.com http://packetstormsecurity.com/files/128136/Mpay24-Payment-Module-1.5-Information-Disclosure-SQL-Injection.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2014/Sep/23 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/69560 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
-
exploit-db.com
/exploits/34586
exploit, patch
-
packetstormsecurity.com
/files/128136/Mpay24-Payment-Module-1.5-Information-Disclosure-SQL-Injection.html
exploit, patch
-
seclists.org
/fulldisclosure/2014/Sep/23
mailing-list, exploit, patch
-
securityfocus.com
/bid/69560
vdb-entry, exploit
-
osvdb.org
/show/osvdb/110737
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95720
vdb-entry
Sources
- CVE List CVE-2014-2008
- NVD CVE-2014-2008
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.