CVE-2013-6839 json
SQL injection vulnerability in InstantSoft InstantCMS 1.10.3 and earlier allows remote attackers to execute arbitrary SQL commands via the…
published 12y ago modified 4mo ago also EUVD-2013-6641
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in InstantSoft InstantCMS 1.10.3 and earlier allows remote attackers to execute arbitrary SQL commands via the orderby parameter to catalog/[id].
Patch / fix
Is CVE-2013-6839 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
- Published
- First public exploit (EDB-30398)
Exploit prediction
1.21% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-30398 InstantCMS 1.10.3 - Blind SQL Injection webapps, 2013-12-17
- htbridge.com https://www.htbridge.com/advisory/HTB23185 referenced PoC, tagged "exploit" by a source, unverified
- archives.neohapsis.com http://archives.neohapsis.com/archives/bugtraq/2013-12/0049.html 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
-
instantcms.ru
/novosti/security-update-1-10-3.html
patch, vendor-advisory
-
htbridge.com
/advisory/HTB23185
exploit
-
archives.neohapsis.com
/archives/bugtraq/2013-12/0049.html
mailing-list, exploit
-
secunia.com
/advisories/56041
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/63842
vdb-entry
Sources
- CVE List CVE-2013-6839
- NVD CVE-2013-6839
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.