SQL Injection

Every one of the 8 is a mark on the map. Named now: 1 to 8, most at risk first.

1. ThinkPHP before 5.1.23 allows SQL Injection via the public/index/index/test/index query string.CVE-2018-16385Thinkphp · 2.2% likely

   CWE-89

2. ThinkPHP v3.2.3 and below contains a SQL injection vulnerability which is triggered when the array is not passed to the "where" and "query" methods.CVE-2020-20120Thinkphp · 1.8% likely

   CWE-89

3. ThinkPHP 3.2.4 has SQL Injection via the order parameter because the Library/Think/Db/Driver.class.php parseOrder function mishandles the key variable.CVE-2018-18546Thinkphp · 1.7% likely

   CWE-89

4. In ThinkPHP 5.1.24, the inner function delete can be used for SQL injection when its WHERE condition's value can be controlled by a user's request.CVE-2018-17566Thinkphp · 1.5% likely

   CWE-89

5. SQL Injection vulnerability exists in ThinkPHP5 5.0.x <=5.1.22 via the parseOrder function in Builder.php.CVE-2021-44350Thinkphp · 1.4% likely

   CWE-89

6. ThinkPHP 5.1.25 has SQL Injection via the count parameter because the library/think/db/Query.php aggregate function mishandles the aggregate variable. NOTE: a backquote character…CVE-2018-18530Thinkphp · 1.2% likely

   CWE-89

7. 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 chara…CVE-2018-18529Thinkphp · 1.2% likely

   CWE-89

8. thinkphp 3.1.3 has SQL Injection via the index.php s parameter.CVE-2018-10225Thinkphp · 1.1% likely

   CWE-89

exploited in the wildcheck availableringed, named or not: CyberSIXT has reported on it

Zoom in on the map and the dots under the middle of it are named where they are.