# CVE-2024-36837: SQL injection in n/a

> A remote attacker can exploit SQL injection in the product list function to obtain sensitive information from the CRMEB e-commerce platform.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 5 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-294q-5vvf-xj65

## What is CVE-2024-36837?

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

### Official description

SQL Injection vulnerability in CRMEB v.5.2.2 allows a remote attacker to obtain sensitive information via the getProductList function in the ProductController.php file.

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

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

It affects 1 product.


Products: Crmeb Crmeb.

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

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

## Is CVE-2024-36837 being exploited?

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

Public exploit code:

- CVE-2024-36837 | CNVD-2024-30128 POC (github_poc): https://github.com/phtcloud-dev/CVE-2024-36837
- CVE-2024-36837 POC (github_poc): https://github.com/lhc321-source/CVE-2024-36837
- CRMEB v.5.2.2 - SQL Injection (nuclei): http/cves/2024/CVE-2024-36837.yaml

## Other vulnerabilities in n/a

- [CVE-2025-25763](https://insights.sbomify.com/CVE-2025-25763/): SQL injection in n/a (critical 9.8)
- [CVE-2023-30185](https://insights.sbomify.com/CVE-2023-30185/): File upload in n/a (critical 9.8)
- [CVE-2020-21787](https://insights.sbomify.com/CVE-2020-21787/): File upload in n/a (critical 9.8)
- [CVE-2020-25466](https://insights.sbomify.com/CVE-2020-25466/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-21394](https://insights.sbomify.com/CVE-2020-21394/): SQL injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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