# CVE-2026-6211: Arbitrary File Upload in Global IT's WEOLL

> Attackers can upload malicious files to execute arbitrary code due to unrestricted file upload in WEOLL.

- **Severity:** High 8.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 12 Jun 2026
- **Also known as:** GHSA-jpfv-gw2p-hjm7

## What is CVE-2026-6211?

CVE-2026-6211 is a high-severity vulnerability in Global IT Informatics Services Inc. WEOLL, published on 12 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Unrestricted upload of file with dangerous type vulnerability in Global IT Informatics Services Inc. WEOLL allows Accessing Functionality Not Properly Constrained by ACLs.

This issue affects WEOLL: from 2.0.9 before 3.2.45.33.

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

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


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

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

## Is CVE-2026-6211 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6211 is a high-severity vulnerability in Global IT Informatics Services Inc. WEOLL, published on 12 Jun 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-6211 in the wild and no public exploit code.

Affected product: Global IT Informatics Services Inc. WEOLL. 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-6211/ (Markdown: https://insights.sbomify.com/CVE-2026-6211/index.md)
```

## Sources

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

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