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

> The MoveIt framework for ROS contains a disputed cross-site scripting vulnerability in its API authentication function with reportedly no impact.

- **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:** 11 May 2023
- **Updated:** 30 May 2025
- **Also known as:** GHSA-q8q9-6wrw-9pjr

## What is CVE-2023-30394?

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

The MoveIt framework 1.1.11 for ROS allows cross-site scripting (XSS) via the API authentication function. NOTE: this issue is disputed by the original reporter because it has "no impact."

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

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

It affects 1 product.


Products: Moveit Moveit.

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

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

## Is CVE-2023-30394 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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