# CVE-2020-21809: NukeViet SQL Injection vulnerability

> SQL injection in NukeViet Shops module allows attackers to manipulate database queries via listid, group_price, or groupid parameters.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m8jx-mxf9-2rpw

## What is CVE-2020-21809?

CVE-2020-21809 is a critical SQL injection vulnerability in n/a, published on 29 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2020-21809?

8 open source packages ship an affected version, including nukeviet/nukeviet. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nukeviet/nukeviet` | Packagist | All versions | None |
| `nukeviet/nukeviet` | Packagist | All versions | None |
| `nukeviet/nukeviet` | Packagist | From 4.0 | 4.0.29 |
| `nukeviet/nukeviet` | Packagist | From 4.0 | 4.0.29 |
| `nukeviet/nukeviet` | Packagist | From 4.1 | 4.1.02 |
| `nukeviet/nukeviet` | Packagist | From 4.1 | 4.1.02 |
| `nukeviet/nukeviet` | Packagist | From 4.2 | 4.2.01 |
| `nukeviet/nukeviet` | Packagist | From 4.2 | 4.2.01 |

Products: Nukeviet Nukeviet.

## How do I fix CVE-2020-21809?

Upgrade nukeviet/nukeviet to a fixed version for your release line: 4.0.29, 4.1.02 or 4.2.01.

## Is CVE-2020-21809 being exploited?

There is no known exploitation of CVE-2020-21809 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-21808](https://insights.sbomify.com/CVE-2020-21808/): NukeViet SQL Injection vulnerability via topicsid parameter (critical 9.8)
- [CVE-2019-7725](https://insights.sbomify.com/CVE-2019-7725/): Deserialization of Untrusted Data in NukeViet (critical 9.8)
- [CVE-2019-7726](https://insights.sbomify.com/CVE-2019-7726/): SQL Injection in NukeViet (critical 9.8)
- [CVE-2020-13155](https://insights.sbomify.com/CVE-2020-13155/): NukeViet Cross-Site Request Forgery (CSRF) (high 8.8)
- [CVE-2020-13156](https://insights.sbomify.com/CVE-2020-13156/): NukeViet Cross-Site Request Forgery (CSRF) (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-21809 and fix it if it is affected.

What it is: CVE-2020-21809 is a critical SQL injection vulnerability in n/a, published on 29 Jul 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-21809 in the wild and no public exploit code.

Affected packages and fixed versions:
- nukeviet/nukeviet (Packagist): affected all versions; no fix listed
- nukeviet/nukeviet (Packagist): affected all versions; no fix listed
- nukeviet/nukeviet (Packagist): affected from 4.0; fixed in 4.0.29
- nukeviet/nukeviet (Packagist): affected from 4.0; fixed in 4.0.29
- nukeviet/nukeviet (Packagist): affected from 4.1; fixed in 4.1.02
- nukeviet/nukeviet (Packagist): affected from 4.1; fixed in 4.1.02
- nukeviet/nukeviet (Packagist): affected from 4.2; fixed in 4.2.01
- nukeviet/nukeviet (Packagist): affected from 4.2; fixed in 4.2.01

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-21809/ (Markdown: https://insights.sbomify.com/CVE-2020-21809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-21809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-21809
- OSV: https://osv.dev/vulnerability/CVE-2020-21809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-21809/
Summaries are generated and may contain mistakes; the official description above is the record.