CVE-2020-21809
CRITICALCVE-2020-21809 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in nukeviet/nukeviet. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2020-21809 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
NukeViet SQL Injection vulnerability
Blast Radius
nukeviet/nukeviet🐘nukeviet/nukeviet🐘nukeviet/nukeviet🐘nukeviet/nukevietReal-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
| 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 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
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
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.