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).

Vulnerability/
CVE-2018-18529

critical

9.8

CWE

19/10/2018

14/5/2022

16/9/2024

CVE-2018-18529: SQL Injection

First published: Fri Oct 19 2018(Updated: )

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.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
composer/topthink/framework	<=3.2.4
ThinkPHP ThinkPHP	=3.2.4

Never miss a vulnerability like this again

Reference Links

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).

collector/github-advisory-latest
alias/GHSA-78q9-24gv-g288
alias/CVE-2018-18529
collector/github-advisory
collector/nvd-index
collector/nvd-cve
agent/author
agent/type
agent/softwarecombine
agent/references
agent/severity
agent/weakness
agent/tags
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/trending
package-manager/composer
vendor/thinkphp
canonical/thinkphp thinkphp
version/thinkphp thinkphp/3.2.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.