CVE-2018-18529: SQL Injection
ThinkPHP 3.2.4 has SQL Injection via the count parameter because the Library/Think/Db/Driver/Mysql.class.php parseKey function mishandles the key variable. NOTE: a backquote character is not required in the attack URI.
Other sources
ThinkPHP 3.2.4 has SQL Injection via the count parameter because the Library/Think/Db/Driver/Mysql.class.php parseKey function mishandles the key variable. NOTE: a backquote character is not required in the attack URI.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2018-18529?
The severity of CVE-2018-18529 is critical with a CVSS score of 9.8.
How does ThinkPHP 3.2.4 have SQL Injection vulnerability?
ThinkPHP 3.2.4 has SQL Injection vulnerability through the count parameter due to mishandling of the key variable in the parseKey function of Mysql.class.php.
What is the affected software version of CVE-2018-18529?
The affected software version of CVE-2018-18529 is ThinkPHP 3.2.4.
How can I fix CVE-2018-18529?
It is recommended to update ThinkPHP to a version that has patched the SQL Injection vulnerability.
Where can I find more information about CVE-2018-18529?
More information about CVE-2018-18529 can be found at the following references: [NVD](https://nvd.nist.gov/vuln/detail/CVE-2018-18529), [Kingkk.com](https://www.kingkk.com/2018/10/Thinkphp-%E8%81%9A%E5%90%88%E6%9F%A5%E8%AF%A2%E6%BC%8F%E6%B4%9E/#ThinkPHP3-lt-3-2-4), [GitHub Advisory](https://github.com/advisories/GHSA-78q9-24gv-g288).