# CVE-2024-58393: i-Netsolution Readymade Unilevel Ecommerce MLM SQL Injection via product-details.php


- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-83x3-gcgq-gcgq

## What is CVE-2024-58393?

CVE-2024-58393 is a high-severity vulnerability in i-Netsolution Readymade Unilevel Ecommerce MLM, published on 22 Oct 2026. 

### Official description

i-Netsolution Readymade Unilevel Ecommerce MLM (2024-03-15 build) contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries through the 'id' parameter. Attackers can send GET requests to /product-details.php with boolean-based, stacked, or time-based SLEEP payloads in 'id' to extract database information. Exploitation evidence was first observed by the Shadowserver Foundation on 2024-09-14.

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

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


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

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

## Is CVE-2024-58393 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-58393 is a high-severity vulnerability in i-Netsolution Readymade Unilevel Ecommerce MLM, published on 22 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-58393 exists.

Affected product: i-Netsolution Readymade Unilevel Ecommerce MLM. 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-58393/ (Markdown: https://insights.sbomify.com/CVE-2024-58393/index.md)
```

## Sources

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

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