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

> Attackers can inject SQL commands via the taille parameter in getCasier.php, potentially reading or modifying database contents.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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:** 23 Jan 2023
- **Updated:** 2 Apr 2025

## What is CVE-2023-22630?

CVE-2023-22630 is a medium-severity SQL injection vulnerability in n/a, published on 23 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IzyBat Orange casiers before 20221102_1 allows SQL Injection via a getCasier.php?taille= URI.

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

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

It affects 1 product.


Products: Izybat Orange Casiers.

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

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

## Is CVE-2023-22630 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-50429](https://insights.sbomify.com/CVE-2023-50429/): SQL injection in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22630 is a medium-severity SQL injection vulnerability in n/a, published on 23 Jan 2023. 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-2023-22630 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-22630/ (Markdown: https://insights.sbomify.com/CVE-2023-22630/index.md)
```

## Sources

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

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