# CVE-2025-6173: Webkul QloApps ajax_products_list.php sql injection

> Remote attackers with admin privileges can execute SQL injection via the packItself argument in QloApps, potentially accessing or modifying database content.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2025
- **Updated:** 17 Jun 2025
- **Also known as:** GHSA-8jj5-jvgv-w755

## What is CVE-2025-6173?

CVE-2025-6173 is a medium-severity SQL injection vulnerability in Webkul QloApps, published on 17 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability classified as critical was found in Webkul QloApps 1.6.1. Affected by this vulnerability is an unknown functionality of the file /admin/ajax_products_list.php. The manipulation of the argument packItself leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The vendor confirms the existence of this flaw but considers it a low-level issue due to admin privilege pre-requisites. Still, a fix is planned for a future release.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-6173?

It affects 1 product.


Products: Webkul Qloapps.

## How do I fix CVE-2025-6173?

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

## Is CVE-2025-6173 being exploited?

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

## Other vulnerabilities in Webkul QloApps

- [CVE-2025-67325](https://insights.sbomify.com/CVE-2025-67325/): File upload in n/a (critical 9.8)
- [CVE-2023-36284](https://insights.sbomify.com/CVE-2023-36284/): SQL injection in n/a (high 7.5)
- [CVE-2024-40318](https://insights.sbomify.com/CVE-2024-40318/): File upload in n/a (high 7.2)
- [CVE-2025-10759](https://insights.sbomify.com/CVE-2025-10759/): Webkul QloApps CSRF Token authorization (medium 6.9)
- [CVE-2023-36235](https://insights.sbomify.com/CVE-2023-36235/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-6173 and fix it if it is affected.

What it is: CVE-2025-6173 is a medium-severity SQL injection vulnerability in Webkul QloApps, published on 17 Jun 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6173 exists.

Affected product: Webkul QloApps. 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-2025-6173/ (Markdown: https://insights.sbomify.com/CVE-2025-6173/index.md)
```

## Sources

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

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