# CVE-2017-12307: Cross-site scripting in Cisco Small Business 300 and 500 Series Managed Switches

> Unauthenticated remote attackers can execute arbitrary script code or access sensitive browser-based information via reflected XSS in Cisco Small Business Managed Switches.

- **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:** 18 Jan 2018
- **Updated:** 2 Dec 2024
- **Also known as:** GHSA-m32m-2q87-9hp4

## What is CVE-2017-12307?

CVE-2017-12307 is a medium-severity cross-site scripting vulnerability in Cisco Small Business 300 and 500 Series Managed Switches, published on 18 Jan 2018. 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

A vulnerability in the web framework of Cisco Small Business Managed Switches software could allow an unauthenticated, remote attacker to conduct a reflected cross-site scripting (XSS) attack against a user of the web interface of an affected system. The vulnerability is due to insufficient input validation of parameters that are passed to the web server of the affected system. An attacker could exploit this vulnerability by convincing a user to follow a malicious link or by intercepting and injecting code into a user request. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected web interface or allow the attacker to access sensitive browser-based information. This vulnerability affects the following Cisco Small Business 300 and 500 Series Managed Switches: Cisco Small Business 300 Series Managed Switches, Cisco Small Business 500 Series Stackable Managed Switches, Cisco 350 Series Managed Switches, Cisco 350X Series Stackable Managed Switches, Cisco 550X Series Stackable Managed Switches, Cisco ESW2 Series Advanced Switches. Cisco Bug IDs: CSCvg24637.

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

## Which versions are affected by CVE-2017-12307?

It affects 85 products.


Products: Cisco Esw2-350g-52 Firmware, Cisco Esw2-350g-52dc Firmware, Cisco Esw2-550x-48 Firmware, Cisco Esw2-550x-48dc Firmware, 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 Sf350-48 Firmware, Cisco Sf350-48mp Firmware, Cisco Sf350-48p Firmware and 65 more.

## How do I fix CVE-2017-12307?

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

## Is CVE-2017-12307 being exploited?

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

## Other vulnerabilities in Cisco Small Business 300 and 500 Series Managed Switches

- [CVE-2017-6720](https://insights.sbomify.com/CVE-2017-6720/): Denial of service in Cisco Small Business Managed Switches (medium 6.5)
- [CVE-2017-12308](https://insights.sbomify.com/CVE-2017-12308/): Cross-site scripting in Cisco Small Business 300 and 500 Series Managed Switches (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-12307 and fix it if it is affected.

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

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

## Sources

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

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