# CVE-2020-21884: Cross-site request forgery in n/a

> Attackers can trick administrators into reconfiguring UniBox network devices via crafted HTTP requests, potentially altering network settings.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Apr 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-2hc7-883f-33cm

## What is CVE-2020-21884?

CVE-2020-21884 is a high-severity vulnerability in n/a, published on 9 Apr 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unibox SMB 2.4 and UniBox Enterprise Series 2.4 and UniBox Campus Series 2.4 contain a cross-site request forgery (CSRF) vulnerability in /tools/network-trace, /list_users, /list_byod?usertype=raduser, /dhcp_leases, /go?rid=202 in which a specially crafted HTTP request may reconfigure the device.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 5 products.


Products: Indionetworks Unibox U1000 Firmware, Indionetworks Unibox U2500 Firmware, Indionetworks Unibox U5000 Firmware, Indionetworks Unibox U500 Firmware, Indionetworks Unibox U50 Firmware.

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

No fix has been published for CVE-2020-21884 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-21884 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-21883](https://insights.sbomify.com/CVE-2020-21883/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-21884 is a high-severity vulnerability in n/a, published on 9 Apr 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-21884 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-21884/ (Markdown: https://insights.sbomify.com/CVE-2020-21884/index.md)
```

## Sources

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

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