# CVE-2026-50542: Xibo: IDOR (Broken Object-Level Authorization) on GET /layout/status/{id} Allows Arbitrary Layout Metadata Disclosure


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/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-wj8r-32gf-6f5f

## What is CVE-2026-50542?

CVE-2026-50542 is a medium-severity vulnerability in xibosignage xibo-cms, published on 28 Oct 2026. 

### Official description

Xibo is an open source digital signage platform with a web content management system and Windows display player software. Prior to 4.4.3, missing access-control checks on `GET /layout/status/{id}` allow an authenticated user with any privileges to view the `status and metadata` of any layout, including layouts for which the user does not have view rights. This issue is fixed in version 4.4.3.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-50542 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50542 is a medium-severity vulnerability in xibosignage xibo-cms, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-50542 in the wild and no public exploit code.

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

## Sources

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

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