# CVE-2023-45359: Cross-site scripting in n/a

> Attackers can inject malicious markup into the Vector Skin toggle button label, leading to cross-site scripting in MediaWiki installations.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2024
- **Updated:** 9 Oct 2024
- **Also known as:** DEBIAN-CVE-2023-45359, GHSA-8w2v-m598-22q3, UBUNTU-CVE-2023-45359

## What is CVE-2023-45359?

CVE-2023-45359 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Vector Skin component for MediaWiki before 1.39.5 and 1.40.x before 1.40.1. vector-toc-toggle-button-label is not escaped, but should be, because the line param can have markup.

Weakness: CWE-116 (Improper Encoding or Escaping of Output)

## Which versions are affected by CVE-2023-45359?


## How do I fix CVE-2023-45359?

Upgrade to a fixed version.

## Is CVE-2023-45359 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-45359 and fix it if it is affected.

What it is: CVE-2023-45359 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45359 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-2023-45359/ (Markdown: https://insights.sbomify.com/CVE-2023-45359/index.md)
```

## Sources

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

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