CVE-2020-21176: SQL injection vulnerability in the model.increment and model.decrement function in ThinkJS 3.2.10 allows remot

Q: How do I fix CVE-2020-21176?

thinkjs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2020-21176 being exploited?

CVE-2020-21176 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-21176 affect?

CVE-2020-21176 affects thinkjs. Severity is critical (CVSS 9.8). 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.

Q: How urgent is CVE-2020-21176?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2020-21176 is a critical-severity flaw (CVSS 9.8) affecting thinkjs. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 26%)
CISA exploited list	No
Weakness	CWE-89
Published	2021-02-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: thinkjs

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-02-01 18:15 UTCPublished CVE record published
2026-06-17 03:03 UTCUpdated Record last modified

thinkjs thinkjs DOWNGRADE

Affected: 3.2.10

Fixed in: no fixed release known

Safe to downgrade to: a release before 3.2.10

1. Check installed version

npm ls thinkjs

2. No fixed release: DOWNGRADE to a release before 3.2.10

npm view thinkjs versions npm install thinkjs@"<3.2.10"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-21176?

thinkjs: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2020-21176 being exploited?

CVE-2020-21176 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-21176 affect?

CVE-2020-21176 affects thinkjs. Severity is critical (CVSS 9.8). 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.

How urgent is CVE-2020-21176?

Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs