Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with standard Notification Centre access
-
ExploitEnumerate sequential notification IDs
-
ExecutionRequest /notification/export/{id} for other users' notifications
-
ImpactExfiltrate administrator attachments
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated Xibo CMS account that holds access to the Notification Centre to view past notifications - a privilege the vendor states is granted to non-administrators as standard, so the bar is low in typical deployments. Given that access, the attacker simply iterates over sequential notification IDs against /notification/export/{id}; no user interaction, no special or non-default configuration, and no administrative rights are needed. The limiting factor is solely the need for a valid account with the standard Notification Centre privilege: a fully unauthenticated attacker cannot exploit this, so risk scales with the number and trust level of CMS user accounts. Impact is bounded to downloading notification attachments and does not extend to modifying data or affecting availability. |
| Impact | This is a genuine but moderate-priority issue, not a top-of-queue emergency. The CVSS 3.1 base score is 6.5 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N - network-reachable and low-complexity, but requiring an authenticated account (PR:L), and the impact is confidentiality-only (C:H, I:N, A:N): the flaw leaks notification attachments but does not let an attacker modify data or disrupt service. The vuln.today Decision label is 'this_month', consistent with a real-but-not-urgent fix window. No EPSS probability was supplied and the CVE is not listed in CISA KEV, so exploitation is not confirmed active - no public exploit identified at time of analysis (the only references are the vendor advisory, fix PR, commits and release notes, i.e. patch artifacts, not exploit code). The signals are internally consistent: medium severity, authenticated-only, confidentiality-only, and a non-emergency decision label all point the same way. The main caveat is that the true sensitivity of the exposed data depends entirely on what administrators attach to notifications, which the sources do not characterize; C:H assumes those attachments can be sensitive. Treat as a standard patch-this-cycle item, with elevated attention where the Xibo CMS has many low-trust user accounts. |
| Exploit ScenarioDerived | A low-privileged but authenticated Xibo CMS user who has the standard Notification Centre privilege enumerates sequential notification IDs and issues requests to /notification/export/{id} for IDs they do not own, downloading attachments from notifications created by administrators. No public exploit was identified, but the technique is simply iterating integer IDs against an existing endpoint, so reproduction is straightforward for any authenticated user. The attack is network-reachable (AV:N) and low-complexity (AC:L) but gated by the need for a valid account (PR:L). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
An authenticated user with standard Notification Centre access in Xibo CMS before 4.4.3 can download notification attachments belonging to any other notification, including administrator-created ones, by iterating sequential notification IDs against the /notification/export/{id} endpoint. The flaw is a missing object-level authorization check (CWE-862): the export route validates that a user is logged in but does not verify that the requested notification belongs to, or is visible to, that user. No public exploit code or active exploitation has been identified at time of analysis, and the vendor considers upgrading to 4.4.3 the complete remediation, with privilege revocation as the interim workaround.
RemediationAI
Vendor-released patch: upgrade Xibo CMS to version 4.4.3, which the advisory names as the fixed release, or track the 4.5.0-beta line; deployment details and the changelog are at https://github.com/xibosignage/xibo-cms/releases/tag/4.4.3. The vendor states that upgrading is necessary to remediate and that organisations unable to upgrade should revoke the Notification Centre 'view past notifications' privilege from users they do not trust - the trade-off being that affected users lose visibility of their notification history through that interface. Operators should also inventory CMS accounts holding that standard privilege, since any such account is sufficient to enumerate sequential notification IDs against /notification/export/{id}; note that no patch-version-independent code-level workaround other than the upstream userNotificationFactory scoping change is described in the available sources.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Xibo CMS is a PHP application (Slim-style controllers under lib/Controller) backed by a notification subsystem in which users receive notifications and notification attachments through a Notification Centre. The affected route, /notification/export/{id}, is meant to stream the attachment associated with a single notification. CWE-862 (Missing Authorization) manifests here because the controller resolves the requested notification by raw ID via the notification factory and then exports its attachment without confirming the notification is addressed to the requesting user. Because notification identifiers are sequential, an authenticated account holding the standard Notification Centre privilege - granted to non-administrators by default - can enumerate IDs and pull attachments from notifications created by administrators or other users. The upstream fix PR 3487 changes the delete/exports path in lib/Controller/Notification.php from the generic notificationFactory->getById($id) lookup to userNotificationFactory->getByNotificationId($id), scoping the object lookup to the current user's notification set; the CVSS:3.1 vector AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N reflects a confidentiality-only impact with no integrity or availability effect and no user interaction, requiring only a low-privileged authenticated session.
Know when Xibo Cms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Web endpoint is network-reachable (AV:N) and trivially triggered by iterating IDs (AC:L); a standard authenticated account is required (PR:L); only attachment confidentiality is affected (C:H, I:N, A:N).
Primary rating from Vendor (GitHub_M).
CVSS VectorVendor: GitHub_M
Lifecycle Timeline
2DescriptionCVE.org
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 object-level authorization on /notification/export/{id} allows an authenticated user to download attachments from any notification, including notifications created by administrators, by iterating over sequential notification IDs. Exploitation requires access to the Notification Centre to view past notifications, a privilege granted to non-administrators as standard. This issue is fixed in version 4.4.3.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
SQL injection in Xibo CMS versions 1.7 through 4.4.0 allows authenticated users with DataSet or Layout access privileges
Server-Side Request Forgery in Xibo CMS versions prior to 4.4.1 lets an authenticated user with Library upload permissio
Stored cross-site scripting in Xibo CMS prior to 4.4.2 allows authenticated users with elevated DataSet privileges to ch
Broken object-level authorization in Xibo CMS 4.4.2 and earlier allows a logged-in user to point PUT and DELETE requests
Missing object-level authorization on the dataset CSV export endpoint in Xibo CMS 4.4.2 and earlier lets a privileged au
Missing object-level authorization on the `GET /layout/status/{id}` endpoint in Xibo CMS 4.4.2 and earlier lets any auth
Missing authorization in Xibo CMS prior to 4.4.3 exposes super admin-restricted module settings and full module entity d
An authenticated user of Xibo CMS can push arbitrary scheduling criteria to any display group through the POST /displayg
EUVD-2026-112139
NVD
CVE.org
Vulnrichment
GitHub
Exploit-DB