# CVE-2023-41262: SQL injection in n/a

> Unauthenticated attackers can execute arbitrary SQL statements via the sorting parameter in the CSV export endpoint, compromising the backend database.

- **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:** 12 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-jgfr-c5jr-627r

## What is CVE-2023-41262?

CVE-2023-41262 is a critical SQL injection vulnerability in n/a, published on 12 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in /fcgi/scrut_fcgi.fcgi in Plixer Scrutinizer before 19.3.1. The csvExportReport endpoint action generateCSV is vulnerable to SQL injection through the sorting parameter, allowing an unauthenticated user to execute arbitrary SQL statements in the context of the application's backend database server.

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

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

It affects 1 product.


Products: Plixer Scrutinizer.

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

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

## Is CVE-2023-41262 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-28993](https://insights.sbomify.com/CVE-2021-28993/): SQL injection in n/a (high 7.5)
- [CVE-2023-41261](https://insights.sbomify.com/CVE-2023-41261/): Missing authorization in n/a (medium 5.3)
- [CVE-2023-41263](https://insights.sbomify.com/CVE-2023-41263/): Information disclosure in n/a (low 3.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41262 is a critical SQL injection vulnerability in n/a, published on 12 Oct 2023. 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-2023-41262 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-41262/ (Markdown: https://insights.sbomify.com/CVE-2023-41262/index.md)
```

## Sources

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

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