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

> Reflected XSS in the User Input field allows attackers to execute arbitrary scripts in victim browsers.

- **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:** 22 May 2023
- **Updated:** 21 Jan 2025
- **Also known as:** GHSA-j3h2-mp8v-c92r

## What is CVE-2023-31584?

CVE-2023-31584 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 May 2023. 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

GitHub repository cu/silicon commit a9ef36 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the User Input field.

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

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

It affects 1 product.


Products: Silicon Project Silicon.

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

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

## Is CVE-2023-31584 being exploited?

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

Public exploit code:

- Public disclosure for CVE-2023-31584. (github_poc): https://github.com/rootd4ddy/CVE-2023-31584

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31584 is a medium-severity cross-site scripting vulnerability in n/a, published on 22 May 2023. 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-2023-31584 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-31584/ (Markdown: https://insights.sbomify.com/CVE-2023-31584/index.md)
```

## Sources

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

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