# CVE-2018-0408: Cross-site scripting in Cisco Small Business 300 Series Managed Switches unknown

> Authenticated attackers can execute arbitrary scripts or steal data via reflected XSS in the Cisco Small Business 300 Series switch web interface.

- **Severity:** Medium 5.4 (`CVSS:3.0/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:** 1 Aug 2018
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-9g7v-p4f2-q8p5

## What is CVE-2018-0408?

CVE-2018-0408 is a medium-severity cross-site scripting vulnerability in Cisco Small Business 300 Series Managed Switches unknown, published on 1 Aug 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in the web-based management interface of Cisco Small Business 300 Series (Sx300) Managed Switches could allow an authenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. The vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected device. An attacker could exploit this vulnerability by persuading a user of the interface to click a crafted link. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface or allow the attacker to access sensitive browser-based information. Cisco Bug IDs: CSCvi87330.

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

## Which versions are affected by CVE-2018-0408?

It affects 28 products.


Products: Cisco Sf300-08 Firmware, Cisco Sf300-24 Firmware, Cisco Sf300-24mp Firmware, Cisco Sf300-24p Firmware, Cisco Sf300-24pp Firmware, Cisco Sf300-48 Firmware, Cisco Sf300-48p Firmware, Cisco Sf300-48pp Firmware, Cisco Sf302-08 Firmware, Cisco Sf302-08mp Firmware, Cisco Sf302-08mpp Firmware, Cisco Sf302-08p Firmware, Cisco Sf302-08pp Firmware, Cisco Sg300-10 Firmware, Cisco Sg300-10mp Firmware, Cisco Sg300-10mpp Firmware, Cisco Sg300-10p Firmware, Cisco Sg300-10pp Firmware, Cisco Sg300-10sfp Firmware, Cisco Sg300-20 Firmware and 8 more.

## How do I fix CVE-2018-0408?

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

## Is CVE-2018-0408 being exploited?

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

## Other vulnerabilities in Cisco Small Business 300 Series Managed Switches unknown

- [CVE-2020-3147](https://insights.sbomify.com/CVE-2020-3147/): Cisco Small Business Switches Denial of Service Vulnerability (high 8.6)
- [CVE-2019-1814](https://insights.sbomify.com/CVE-2019-1814/): Cisco Small Business 300 Series Managed Switches DHCP Denial of Service Vulnerability (medium 6.8)
- [CVE-2018-0465](https://insights.sbomify.com/CVE-2018-0465/): Cisco Small Business 300 Series Managed Switches Cross-Site Scripting Vulnerability (medium 6.1)
- [CVE-2018-0407](https://insights.sbomify.com/CVE-2018-0407/): Cross-site scripting in Cisco Small Business 300 Series Managed Switches unknown (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-0408 and fix it if it is affected.

What it is: CVE-2018-0408 is a medium-severity cross-site scripting vulnerability in Cisco Small Business 300 Series Managed Switches unknown, published on 1 Aug 2018. 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-2018-0408 in the wild and no public exploit code.

Affected product: Cisco Small Business 300 Series Managed Switches unknown. 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-2018-0408/ (Markdown: https://insights.sbomify.com/CVE-2018-0408/index.md)
```

## Sources

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

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