# CVE-2024-21514: SQL injection in opencart

> Unauthenticated attackers can exploit SQL injection in the Divido payment extension to dump the entire OpenCart database, exposing customer PII.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-7crj-24g3-g7h7

## What is CVE-2024-21514?

CVE-2024-21514 is a high-severity SQL injection vulnerability in opencart/opencart, published on 22 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This affects versions of the package opencart/opencart from 0.0.0. An SQL Injection issue was identified in the Divido payment extension for OpenCart, which is included by default in version 3.0.3.9. As an anonymous unauthenticated user, if the Divido payment module is installed (it does not have to be enabled), it is possible to exploit SQL injection to gain unauthorised access to the backend database. For any site which is vulnerable, any unauthenticated user could exploit this to dump the entire OpenCart database, including customer PII data.

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

## Which versions are affected by CVE-2024-21514?

2 open source packages ship an affected version, including opencart/opencart. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `opencart/opencart` | Packagist | All versions to 3.0.3.9 | None |
| `opencart/opencart` | Packagist | All versions to 3.0.3.9 | None |

Products: Opencart Opencart.

## How do I fix CVE-2024-21514?

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

## Is CVE-2024-21514 being exploited?

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

Public exploit code:

- SQL Injection POC for CVE-2024-21514: Divido payment extension for OpenCart (github_poc): https://github.com/bigb0x/CVE-2024-21514

## Other vulnerabilities in opencart/opencart

- [CVE-2023-40834](https://insights.sbomify.com/CVE-2023-40834/): Auth bypass in n/a (critical 9.8)
- [CVE-2014-3990](https://insights.sbomify.com/CVE-2014-3990/): Deserialization in n/a (critical 9.8)
- [CVE-2024-58341](https://insights.sbomify.com/CVE-2024-58341/): OpenCart Core 4.0.2.3 SQL Injection via search Parameter (high 8.8)
- [CVE-2023-47444](https://insights.sbomify.com/CVE-2023-47444/): Code injection in n/a (high 8.8)
- [CVE-2018-13067](https://insights.sbomify.com/CVE-2018-13067/): OpenCart Cross-Site Request Forgery (CSRF) (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-21514 and fix it if it is affected.

What it is: CVE-2024-21514 is a high-severity SQL injection vulnerability in opencart/opencart, published on 22 Jun 2024. 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-2024-21514 exists.

Affected packages and fixed versions:
- opencart/opencart (Packagist): affected all versions up to 3.0.3.9; no fix listed
- opencart/opencart (Packagist): affected all versions up to 3.0.3.9; 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-2024-21514/ (Markdown: https://insights.sbomify.com/CVE-2024-21514/index.md)
```

## Sources

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

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