# CVE-2026-75496: Webkul QloApps improper file upload validation

> An authenticated administrator can upload executable files to achieve remote code execution due to improper file validation in QloApps.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 25 Aug 2026
- **Also known as:** GHSA-2q2p-6wq8-66hp

## What is CVE-2026-75496?

CVE-2026-75496 is a high-severity vulnerability in Webkul QloApps, published on 25 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Webkul QloApps does not perform proper validation on uploaded file extensions or MIME types before moving the file to a publicly accessible directory. A remote, authenticated attacker with administrative privileges could upload executable files and achieve remote code execution. Fixed in 153ec1c.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2026-75496?


## How do I fix CVE-2026-75496?

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

## Is CVE-2026-75496 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75496 and fix it if it is affected.

What it is: CVE-2026-75496 is a high-severity vulnerability in Webkul QloApps, published on 25 Aug 2026. 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-2026-75496 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-2026-75496/ (Markdown: https://insights.sbomify.com/CVE-2026-75496/index.md)
```

## Sources

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

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