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

> Attackers can exploit SQL injection in Voipmonitor GUI to escalate privileges to Administrator level.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-655g-pxvh-gr5j

## What is CVE-2022-24260?

CVE-2022-24260 is a critical SQL injection vulnerability in n/a, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A SQL injection vulnerability in Voipmonitor GUI before v24.96 allows attackers to escalate privileges to the Administrator level.

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

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

It affects 1 product.


Products: Voipmonitor Voipmonitor.

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

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

## Is CVE-2022-24260 being exploited?

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

Public exploit code:

- VoipMonitor - Pre-Auth SQL Injection (nuclei): http/cves/2022/CVE-2022-24260.yaml

## Other vulnerabilities in n/a

- [CVE-2021-41408](https://insights.sbomify.com/CVE-2021-41408/): SQL injection in n/a (critical 9.8)
- [CVE-2022-24259](https://insights.sbomify.com/CVE-2022-24259/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-30461](https://insights.sbomify.com/CVE-2021-30461/): Code injection in n/a (critical 9.8)
- [CVE-2022-24262](https://insights.sbomify.com/CVE-2022-24262/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24260 is a critical SQL injection vulnerability in n/a, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24260 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-2022-24260/ (Markdown: https://insights.sbomify.com/CVE-2022-24260/index.md)
```

## Sources

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

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