CVE-2014-2009 json
The mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to obtain credentials, the installation path, and other sensiti…
published 2014-09-12 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2061
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 7.4%
- EPSS 7.4% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
The mPAY24 payment module before 1.6 for PrestaShop allows remote attackers to obtain credentials, the installation path, and other sensitive information via a direct request to api/curllog.log.
Timeline
- First public exploit (EDB-34586)
- Published
Exploit prediction
7.41% chance of exploitation in the next 30 days, higher than 94% 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 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
exploit-db.com
/exploits/34586
exploit
-
packetstormsecurity.com
/files/128136/Mpay24-Payment-Module-1.5-Information-Disclosure-SQL-Injection.html
exploit
-
seclists.org
/fulldisclosure/2014/Sep/23
mailing-list, exploit
-
securityfocus.com
/bid/69560
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/95721
vdb-entry
-
osvdb.org
/show/osvdb/110738
vdb-entry
Sources
- CVE List CVE-2014-2009
- NVD CVE-2014-2009
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.