# CVE-2026-52730: Xibo CMS Missing Authorization in Module::settingsForm due to PHP operator precedence

> Authorized users with Module View access can view super admin-restricted module settings and leak full module entities due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A: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:** 31 Aug 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-6h64-j36j-h2v2

## What is CVE-2026-52730?

CVE-2026-52730 is a medium-severity missing authorization vulnerability in xibosignage xibo-cms, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### 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 Authorization in Module::settingsForm allows to view (not change) super admin-restricted module settings and leak the full module entity. Exploitation of the vulnerability is possible on behalf of an authorized user who has access to the Module View feature, which are not granted to non-admins as standard. Users should upgrade to version 4.4.3 which fixes this issue. Upgrading to a fixed version is necessary to remediate. Users unable to upgrade should revoke such privileges from users they do not trust.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-52730 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52730 is a medium-severity missing authorization vulnerability in xibosignage xibo-cms, published on 31 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-52730 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-52730/ (Markdown: https://insights.sbomify.com/CVE-2026-52730/index.md)
```

## Sources

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

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