# CVE-2022-41513: SQL injection in n/a

> Attackers can exploit SQL injection in the Online Diagnostic Lab Management System to read or modify database contents via the id parameter.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-v5vm-467h-c574

## What is CVE-2022-41513?

CVE-2022-41513 is a high-severity SQL injection vulnerability in n/a, published on 7 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Online Diagnostic Lab Management System v1.0 was discovered to contain a SQL injection vulnerability via the id parameter at /diagnostic/edittest.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2022-41513?

It affects 1 product.


Products: Online Diagnostic Lab Management System Project Online Diagnostic Lab Management System.

## How do I fix CVE-2022-41513?

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

## Is CVE-2022-41513 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-43135](https://insights.sbomify.com/CVE-2022-43135/): SQL injection in n/a (critical 9.8)
- [CVE-2022-43058](https://insights.sbomify.com/CVE-2022-43058/): SQL injection in n/a (critical 9.8)
- [CVE-2022-42064](https://insights.sbomify.com/CVE-2022-42064/): SQL injection in n/a (critical 9.8)
- [CVE-2022-37152](https://insights.sbomify.com/CVE-2022-37152/): SQL injection in n/a (critical 9.8)
- [CVE-2022-43226](https://insights.sbomify.com/CVE-2022-43226/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41513 and fix it if it is affected.

What it is: CVE-2022-41513 is a high-severity SQL injection vulnerability in n/a, published on 7 Oct 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41513 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-2022-41513/ (Markdown: https://insights.sbomify.com/CVE-2022-41513/index.md)
```

## Sources

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

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