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

> Remote attackers can execute arbitrary code via XSS in multiple input fields of the School Fees Management System.

- **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:** 29 Feb 2024
- **Updated:** 16 Aug 2024
- **Also known as:** GHSA-g22p-98cv-w94f

## What is CVE-2023-51800?

CVE-2023-51800 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Feb 2024. 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

Cross Site Scripting (XSS) vulnerability in School Fees Management System v.1.0 allows a remote attacker to execute arbitrary code via a crafted payload to the main_settings component in the phone, address, bank, acc_name, acc_number parameters, new_class and cname parameter, add_new_parent function in the name email parameters, new_term function in the tname parameter, and the edit_student function in the name parameter.

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

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

It affects 1 product.


Products: School Fees Management System Project School Fees Management System1.0.

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

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

## Is CVE-2023-51800 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51800 exists.

Public exploit code:

- Multiple cross-site scripting (XSS) vulnerabilities in School Fees Management System v1.0. (github_poc): https://github.com/geraldoalcantara/CVE-2023-51800

## Fix prompt for AI coding agents

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

What it is: CVE-2023-51800 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Feb 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51800 exists.

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-51800/ (Markdown: https://insights.sbomify.com/CVE-2023-51800/index.md)
```

## Sources

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

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