# CVE-2023-5047: SQLi in DRDrive

> An SQL injection vulnerability in DRDrive allows attackers to manipulate database queries, potentially exposing or altering sensitive fleet leasing data.

- **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:** 22 Nov 2023
- **Updated:** 21 May 2026
- **Also known as:** GHSA-gfq8-cvv8-37wf

## What is CVE-2023-5047?

CVE-2023-5047 is a critical SQL injection vulnerability in DRDrive, published on 22 Nov 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 DRD Fleet Leasing DRDrive allows SQL Injection.

This issue affects DRDrive: before 20231006.

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

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

It affects 1 product.


Products: Drd Drdrive.

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

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

## Is CVE-2023-5047 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5047 is a critical SQL injection vulnerability in DRDrive, published on 22 Nov 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-5047 in the wild and no public exploit code.

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

## Sources

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

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