Quick answers
- Is CVE-2026-50539 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50539 being exploited in the wild.
- How severe is CVE-2026-50539?
- Medium severity, with a CVSS score of 6.5, published 28 October 2026.
- Which products and versions are affected?
- Xibo CMS prior to 4.4.3.
- Is there a fix for CVE-2026-50539?
- Yes: fixed in 4.4.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50539 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-50539?
- Check whether you run Xibo CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 4.4.3
Technical details
Missing object-level authorization on the `/notification/export/{id}` endpoint in the Notification controller allows an authenticated, unprivileged user to export attachments from any notification by iterating notification IDs. The vulnerable code called `getById()` instead of a permission-checked method like `getByNotificationId()` through the `userNotificationFactory`, enabling horizontal privilege escalation. The fix restricts attachment export to only those notifications the user has explicit access to.
Affected products
- Xibo CMS prior to 4.4.3
Timeline
- 2026-10-28: disclosed