# CVE-2023-47438: SQL Injection vulnerability in Reportico Till

> Attackers can exploit SQL injection in Reportico to obtain sensitive system information via the project parameter.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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:** 27 Mar 2024
- **Updated:** 4 Sep 2024
- **Also known as:** GHSA-jjf4-959w-f545

## What is CVE-2023-47438?

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

### Official description

SQL Injection vulnerability in Reportico Till 8.1.0 allows attackers to obtain sensitive information or other system information via the project parameter.

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

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

2 open source packages ship an affected version, including reportico-web/reportico.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `reportico-web/reportico` | Packagist | All versions to 8.1.0 | None |
| `reportico-web/reportico` | Packagist | All versions to 8.1.0 | None |

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

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

## Is CVE-2023-47438 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-47438 is a medium-severity SQL injection vulnerability in n/a, published on 27 Mar 2024. 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-47438 exists.

Affected packages and fixed versions:
- reportico-web/reportico (Packagist): affected all versions up to 8.1.0; no fix listed
- reportico-web/reportico (Packagist): affected all versions up to 8.1.0; no fix listed

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

## Sources

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

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