# CVE-2024-50983: Cross-site scripting in n/a

> Authenticated administrators can inject arbitrary JavaScript into user browsers via the Last Name field in user management sections.

- **Severity:** Medium 6.1 (`CVSS:3.1/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:** 15 Nov 2024
- **Updated:** 18 Nov 2024
- **Also known as:** GHSA-pww8-r4pc-9m94

## What is CVE-2024-50983?

CVE-2024-50983 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

FlightPath 7.5 contains a Cross Site Scripting (XSS) vulnerability, which allows authenticated remote attackers with administrative rights to inject arbitrary JavaScript in the web browser of a user by including a malicious payload into the Last Name section in the Create/Edit Faculty/Staff User or Create/Edit Student User sections.

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

## Which versions are affected by CVE-2024-50983?

It affects 1 product.


Products: Getflightpath Flightpath.

## How do I fix CVE-2024-50983?

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

## Is CVE-2024-50983 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15227](https://insights.sbomify.com/CVE-2019-15227/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-13396](https://insights.sbomify.com/CVE-2019-13396/): Path traversal in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-50983 and fix it if it is affected.

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

## Sources

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

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