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

> A remote attacker can execute arbitrary code via the Test Name parameter in the online diagnostic lab management system.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 31 Oct 2024
- **Updated:** 31 Oct 2024
- **Also known as:** GHSA-9v8c-rf9v-pf96

## What is CVE-2024-51430?

CVE-2024-51430 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cross Site Scripting vulnerability in online diagnostic lab management system using php v.1.0 allows a remote attacker to execute arbitrary code via the Test Name parameter on the diagnostic/add-test.php component.

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

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


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

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

## Is CVE-2024-51430 being exploited?

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

Public exploit code:

- The Online Diagnostic Lab Management System has a security problem called Cross-Site Scripting (XSS) in the Borrower section. (github_poc): https://github.com/BLACK-SCORP10/CVE-2024-51430

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51430 is a medium-severity cross-site scripting vulnerability in n/a, published on 31 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51430 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-2024-51430/ (Markdown: https://insights.sbomify.com/CVE-2024-51430/index.md)
```

## Sources

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

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