# CVE-2026-16065: Welcart e-Commerce < 2.11.32 - Editor+ SQL Injection via CSV Import

> Editors can execute SQL injection via CSV import in Welcart e-Commerce, allowing unauthorized database access and modification.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-xgjq-gf22-rvwq

## What is CVE-2026-16065?

CVE-2026-16065 is a medium-severity SQL injection vulnerability in Unknown Welcart e-Commerce, published on 6 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Welcart e-Commerce WordPress plugin before 2.11.32 does not properly sanitise a value taken from an imported CSV file before using it in a SQL statement, allowing users with the Editor role and above (including its custom shop-management roles) to perform SQL injection attacks.

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

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


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

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

## Is CVE-2026-16065 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16065 is a medium-severity SQL injection vulnerability in Unknown Welcart e-Commerce, published on 6 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-16065 exists.

Affected product: Unknown Welcart e-Commerce. 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-16065/ (Markdown: https://insights.sbomify.com/CVE-2026-16065/index.md)
```

## Sources

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

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