# CVE-2026-111351: metasfresh through 5.175 Authorization Bypass via /rest/api/board REST API

> Authenticated low-privilege users can bypass authorization checks to read and modify board records outside their assigned scope.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-v43m-w632-85qf

## What is CVE-2026-111351?

CVE-2026-111351 is a low-severity missing authorization vulnerability in metasfresh, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

metasfresh through 5.175 contains a missing record-level authorization vulnerability in BoardRestController that allows authenticated low-privilege users to bypass role and organization access checks. Attackers can call the getBoard, getCard, addCard, removeCard and patchCard handlers to read records outside their scope and modify board card assignments.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-111351 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111351 is a low-severity missing authorization vulnerability in metasfresh, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111351 exists.

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

## Sources

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

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