CVE-2015-1372 json
SQL injection vulnerability in ferretCMS 1.0.4-alpha allows remote attackers to execute arbitrary SQL commands via the p parameter in an up…
published 11y ago modified 4mo ago also EUVD-2015-1509
- 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 83%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in ferretCMS 1.0.4-alpha allows remote attackers to execute arbitrary SQL commands via the p parameter in an update action to admin.php.
Is CVE-2015-1372 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-35914)
- Published
Exploit prediction
2.36% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-35914 ferretCMS 1.0.4-alpha - Multiple Vulnerabilities webapps, 2015-01-26
- openwall.com http://www.openwall.com/lists/oss-security/2015/01/23/3 referenced PoC, tagged "exploit" by a source, unverified
- sroesemann.blogspot.de http://sroesemann.blogspot.de/2015/01/report-for-advisory-sroeadv-2015-10.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2015/Jan/98 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
-
openwall.com
/lists/oss-security/2015/01/23/3
mailing-list, exploit
-
sroesemann.blogspot.de
/2015/01/report-for-advisory-sroeadv-2015-10.html
exploit
-
seclists.org
/fulldisclosure/2015/Jan/98
mailing-list, exploit
- github.com /JRogaishio/ferretCMS/issues/63
-
securityfocus.com
/bid/72287
vdb-entry
Sources
- CVE List CVE-2015-1372
- NVD CVE-2015-1372
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.