# CVE-2026-111691: WIMOOR through commit ec86736 Authentication Bypass via Forged X-USERINFO Header

> Attackers can bypass authentication by forging headers to impersonate admins and access sensitive tenant data in WIMOOR ERP.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-h72p-hrwq-pw25

## What is CVE-2026-111691?

CVE-2026-111691 is a critical authentication bypass vulnerability in wimoor-erp wimoor, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

WIMOOR through commit ec86736 contains an authentication bypass vulnerability that allows attackers to impersonate any tenant and privilege level by sending an unsigned X-USERINFO header. Attackers reaching backend service ports directly, bypassing the gateway, can forge companyid and manager or admin usertype values to read and modify other tenants' orders, finance data, and Amazon seller authorizations.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-111691 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111691 is a critical authentication bypass vulnerability in wimoor-erp wimoor, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111691 in the wild and no public exploit code.

Affected product: wimoor-erp wimoor. 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-111691/ (Markdown: https://insights.sbomify.com/CVE-2026-111691/index.md)
```

## Sources

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

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