# CVE-2021-43661: Cross-site scripting in n/a

> A reflected cross-site scripting vulnerability in the TOTOLink EX300_v2 router allows attackers to inject malicious scripts via the home.asp component.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 30 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hg29-53rh-m9vp

## What is CVE-2021-43661?

CVE-2021-43661 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Mar 2022. 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

totolink EX300_v2 V4.0.3c.140_B20210429 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the component /home.asp.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-43661?

It affects 1 product.


Products: Totolink Ex300 V2 Firmware.

## How do I fix CVE-2021-43661?

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

## Is CVE-2021-43661 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-32449](https://insights.sbomify.com/CVE-2022-32449/): Command injection in n/a (critical 9.8)
- [CVE-2021-43664](https://insights.sbomify.com/CVE-2021-43664/): Command injection in n/a (high 8.1)
- [CVE-2021-43663](https://insights.sbomify.com/CVE-2021-43663/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-43661 and fix it if it is affected.

What it is: CVE-2021-43661 is a medium-severity cross-site scripting vulnerability in n/a, published on 30 Mar 2022. 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-2021-43661 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-2021-43661/ (Markdown: https://insights.sbomify.com/CVE-2021-43661/index.md)
```

## Sources

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

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