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

> Stored XSS in the WLAN SSID parameter allows attackers to execute malicious scripts affecting all privileged users of the device.

- **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:** 28 Oct 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c3r4-m47f-pmm3

## What is CVE-2020-27980?

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

### Official description

Genexis Platinum-4410 P4410-V2-1.28 devices allow stored XSS in the WLAN SSID parameter. This could allow an attacker to perform malicious actions in which the XSS popup will affect all privileged users.

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

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

It affects 1 product.


Products: Genexis Platinum-4410 Firmware.

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

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

## Is CVE-2020-27980 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-6170](https://insights.sbomify.com/CVE-2020-6170/): Auth bypass in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-27980 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Oct 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-27980 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-27980/ (Markdown: https://insights.sbomify.com/CVE-2020-27980/index.md)
```

## Sources

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

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