# CVE-2023-1153: SQLi in Pacsrapor

> Attackers can execute arbitrary SQL commands and potentially run system commands via SQL injection in Pacsrapor.

- **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:** 21 Mar 2023
- **Updated:** 1 Jun 2026
- **Also known as:** GHSA-62wg-rr9j-v622

## What is CVE-2023-1153?

CVE-2023-1153 is a critical SQL injection vulnerability in Pacsrapor, published on 21 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Pacsrapor allows SQL Injection, Command Line Execution through SQL Injection.

This issue affects Pacsrapor: before 1.22.

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

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

It affects 1 product.


Products: Pacsrapor Pacsrapor.

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

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

## Is CVE-2023-1153 being exploited?

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

## Other vulnerabilities in Pacsrapor

- [CVE-2023-1154](https://insights.sbomify.com/CVE-2023-1154/): XSS in Pacsrapor (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1153 is a critical SQL injection vulnerability in Pacsrapor, published on 21 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1153 in the wild and no public exploit code.

Affected product: Pacsrapor. 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-1153/ (Markdown: https://insights.sbomify.com/CVE-2023-1153/index.md)
```

## Sources

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

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