SQL Injection in thinkjs

published 2021-02-01 5y ago modified 2026-06-17 4mo ago also GHSA-q5mq-6fjg-4mw8 , EUVD-2021-2378

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.5%; EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits: 0; none known

SQL injection vulnerability in the model.increment and model.decrement function in ThinkJS 3.2.10 allows remote attackers to execute arbitrary SQL commands via the step parameter.

Is CVE-2020-21176 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.51% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

blog.jiguang.xyz https://blog.jiguang.xyz/posts/thinkjs-sql-injection/ referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
npm	thinkjs	<=3.2.14	no fix listed

Classification

Weakness

CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

blog.jiguang.xyz /posts/thinkjs-sql-injection/
exploit, third-party-advisory
github.com /thinkjs/thinkjs
package, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2020-21176
advisory
blog.jiguang.xyz /posts/thinkjs-sql-injection
web

Sources

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.