How severe is CVE-2020-21809?

CVE-2020-21809 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-21809?

CVE-2020-21809 affects the following packages: nukeviet/nukeviet (Packagist), nukeviet/nukeviet (Packagist), nukeviet/nukeviet (Packagist), nukeviet/nukeviet (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2020-21809?

Update nukeviet/nukeviet to 4.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-21809 is resolved across your whole dependency graph.

How do I detect CVE-2020-21809 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nukeviet/nukeviet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate CVE-2020-21809 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2020-21809?

O3 pinpoints whether CVE-2020-21809 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2020-21809 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2020-21809, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-21809?

CVE-2020-21809 has an EPSS (Exploit Prediction Scoring System) score of 1.6%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2020-21809 published, and has it been updated?

CVE-2020-21809 was published on July 30, 2021 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

CVE-2020-21809

CRITICAL

NukeViet SQL Injection vulnerability

Also known asGHSA-m8jx-mxf9-2rpw

Published

Jul 30, 2021

Updated

Apr 10, 2026

Affected

4 pkgs

Patched

3 / 4

Exploits

2 known

EPSS Exploitation Probability

via FIRST.org ↗

1.6%probability of exploitation in next 30 days

Lower Risk72th percentile+0.99%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected

🐘nukeviet/nukeviet🐘nukeviet/nukeviet🐘nukeviet/nukeviet🐘nukeviet/nukeviet

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

SQL Injection vulnerability in NukeViet CMS module Shops 4.0.29 and 4.3 via the (1) listid parameter in detail.php and the (2) group_price or groupid parameters in search_result.php.

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`nukeviet/nukeviet`	≥ 4.0&&< 4.0.29	4.0.29
🐘Packagist	`nukeviet/nukeviet`	≥ 4.1&&< 4.1.02	4.1.02
🐘Packagist	`nukeviet/nukeviet`	≥ 4.2&&< 4.2.01	4.2.01
🐘Packagist	`nukeviet/nukeviet`	all versions	No fix

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

SQL Injection vulnerability in NukeViet CMS module Shops 4.0.29 and 4.3 …

whitehub.netNVDAug 2021

SQL Injection vulnerability in NukeViet CMS module Shops 4.0.29 and 4.3 …

whitehub.netNVDAug 2021

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for nukeviet/nukeviet. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update nukeviet/nukeviet to 4.0.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-21809 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2020-21809 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2020-21809. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

SQL Injection vulnerability in NukeViet CMS module Shops 4.0.29 and 4.3 via the (1) listid parameter in detail.php and the (2) group_price or groupid parameters in search_result.php.

O3 Security · Impact-Aware SCA

Is CVE-2020-21809 in your dependencies?

O3 detects CVE-2020-21809 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works