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

> Remote attackers can extract sensitive information via SQL injection in the HC Mailinspector whitelist component.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/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:** 7 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4rfv-qq74-7p4v

## What is CVE-2024-32369?

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

### Official description

SQL Injection vulnerability in HSC Cybersecurity HC Mailinspector 5.2.17-3 through 5.2.18 allows a remote attacker to obtain sensitive information via a crafted payload to the start and limit parameter in the mliWhiteList.php component.

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

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

It affects 1 product.


Products: Hsclabs Mailinspector.

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

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

## Is CVE-2024-32369 being exploited?

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

Public exploit code:

- Description: SQL Injection vulnerability in HSC Cybersecurity HSC Mailinspector v.5.2.17-3 allows a remote attacker to obtain sensitive information via a crafted payload to the start and limit parameter in the mliWhiteList.php component. (github_poc): https://github.com/chucrutis/CVE-2024-32369

## Other vulnerabilities in n/a

- [CVE-2024-32370](https://insights.sbomify.com/CVE-2024-32370/): Information disclosure in n/a (critical 9.8)
- [CVE-2024-34470](https://insights.sbomify.com/CVE-2024-34470/): Path traversal in n/a (high 8.6)
- [CVE-2026-29962](https://insights.sbomify.com/CVE-2026-29962/): Path traversal in n/a (high 7.5)
- [CVE-2026-29963](https://insights.sbomify.com/CVE-2026-29963/): Path traversal in n/a (high 7.5)
- [CVE-2024-32371](https://insights.sbomify.com/CVE-2024-32371/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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