# CVE-2026-111032: Welcart e-Commerce < 2.12.6 - Author+ Arbitrary Product SKU Update and Disclosure via item_sku_ajax


- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-3rmh-w7g6-4jgh

## What is CVE-2026-111032?

CVE-2026-111032 is a low-severity vulnerability in Unknown Welcart e-Commerce, published on 28 Oct 2026. 

### Official description

The Welcart e-Commerce WordPress plugin before 2.12.6 does not properly verify authorization against the targeted product before processing SKU changes, because its capability check is not tied to the product being edited, allowing any authenticated user with Author-level access or higher to read, modify, create, delete and re-order the SKU data (including prices, confidential cost prices and stock levels) of any product, including those belonging to other users.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-111032 being exploited?

There is no known exploitation of CVE-2026-111032 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111032 is a low-severity vulnerability in Unknown Welcart e-Commerce, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-111032 in the wild and no public exploit code.

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-111032/ (Markdown: https://insights.sbomify.com/CVE-2026-111032/index.md)
```

## Sources

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

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