# CVE-2020-24061: Cross-site scripting in n/a

> Attackers can execute arbitrary code and steal cookies via XSS in the KASDA KW5515 router firewall menu.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Sep 2024
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-6c6w-688f-8mwx

## What is CVE-2020-24061?

CVE-2020-24061 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross Site Scripting (XSS) Vulnerability in Firewall menu in Control Panel in KASDA KW5515 version 4.3.1.0, allows attackers to execute arbitrary code and steal cookies via a crafted script

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

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

It affects 1 product.


Products: Kasdanet Kw5515 Firmware.

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

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

## Is CVE-2020-24061 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-24061 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2020-24061 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 Sep 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-24061 exists.

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

## Sources

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

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