Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate to Xibo CMS as any user
-
DeliveryCraft POST to /displaygroup/criteria/{displayGroupId}
-
ExploitSubmit criteria for an unauthorized display group
-
ExecutionMissing ACL check accepts request
-
PersistCriteria pushed to player via XMR
-
ImpactScheduled playback altered on target display
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 | Requires (1) an authenticated account on the Xibo CMS, since the vulnerable POST /displaygroup/criteria/{displayGroupId} endpoint is reachable only after login (PR:L), and (2) the optional 'Schedule Criteria' feature to be actively in use on the CMS, as stated by the vendor advisory - without it there are no criteria updates to abuse. The limiting factors are therefore the need for valid CMS credentials and this non-default scheduling configuration; impact is confined to integrity of display scheduling/playback (no data disclosure, code execution, or outage). The fix enforces checkEditable on the target display group and adds FeatureAuth requiring displaygroup.modify/displays.modify permissions. |
| Impact | This is a genuine but low-urgency issue rather than a top-priority emergency. The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, base 4.3) describes a network-reachable, low-complexity flaw that nonetheless requires an authenticated CMS user (PR:L) and yields only limited integrity impact (I:L) with no confidentiality or availability loss. The vendor's own GHSA and the patch diff confirm the root cause (CWE-862 missing authorization): the POST /displaygroup/criteria/{displayGroupId} handler never called checkEditable on the target display group, so any authenticated user could push scheduling criteria to displays they do not own. No EPSS score and no KEV listing were supplied, and there is no public exploit reference in the input - only the advisory, PR, commit, and release links - so exploitation status is 'no public exploit identified at time of analysis.' The vuln.today Decision label is this_month, consistent with the modest impact: an attacker can skew scheduled playback (e.g. trigger rainy-weather content on a clear day) but cannot read data, run code, or take down the service. These signals align rather than conflict; the only notable caveat is that exploitation is gated on the optional 'Schedule Criteria' feature actually being in use, which narrows the real-world exposed population below what the network vector alone suggests. |
| Exploit ScenarioDerived | An authenticated low-privilege user of a Xibo CMS where Schedule Criteria is in use sends a crafted POST to /displaygroup/criteria/{displayGroupId} targeting a display group they have no rights over. Because the endpoint omitted the authorization check, the criteria update is relayed to the player via XMR and alters what content the display shows, overriding the intended schedule. No public exploit code is referenced in the available sources; the trigger is a simple authenticated HTTP request with low attack complexity. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
An authenticated user of Xibo CMS can push arbitrary scheduling criteria to any display group through the POST /displaygroup/criteria/{displayGroupId} endpoint, which performs no ownership or permission check on the target group, so the update is relayed over XMR to player devices that should belong to someone else. The result is altered playback - for example weather-dependent content being shown when the condition it depends on is false - but only on installations where the optional Schedule Criteria feature is actually in use, and impact is limited to the integrity of scheduling data (no disclosure, no code execution, no outage). Xibo CMS versions up to and including 4.4.2 are affected and the issue is fixed in 4.4.3; no public exploit code or active exploitation has been reported, and the vendor rates it low severity (CVSS 4.3, PR:L).
RemediationAI
Upgrade to Xibo CMS 4.4.3 or later, which contains both hardening changes: the pushCriteriaUpdate() controller now calls checkEditable() on the target display group and the /displaygroup/criteria/{displayGroupId} route is protected by FeatureAuth requiring displaygroup.modify or displays.modify (fix PR https://github.com/xibosignage/xibo-cms/pull/3488, commits 93587cf872392e91534bb50aa6be071821383e25 and aeca5d6bfbc5eb8a825e6950913c9ab25dc9edc0, release https://github.com/xibosignage/xibo-cms/releases/tag/4.4.3). Vendor-released patch: 4.4.3. The advisory notes that upgrading is necessary to remediate; for administrators who cannot upgrade immediately, the stated workaround is to revoke CMS access from any users they do not trust, with the trade-off that this removes those accounts' legitimate authoring and scheduling capabilities, and additionally not relying on Schedule Criteria for conditional playback until the upgrade is applied.
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 web application (Slim-based routing, Doctrine-style factories, controllers under lib/Controller) that manages digital signage displays through a Windows player client; the CMS and players communicate over XMR, the Xibo Message Relay message bus, which carries control messages such as criteria updates. The flaw is CWE-862 (Missing Authorization): the DisplayGroup controller action pushCriteriaUpdate() accepted a displayGroupId straight from the route and dispatched a criteria update to that group without ever loading the group and calling checkEditable() on it, and the route in lib/routes.php was registered without the FeatureAuth middleware. The upstream fix does both - it fetches the display group by ID and throws AccessDeniedException when the current user lacks edit rights, and it attaches FeatureAuth requiring the displaygroup.modify or displays.modify permission to the route. Criteria are the inputs used by the CMS scheduling engine to decide whether conditional content (for instance a rain-weather content item) should play, which explains the integrity-only impact: an attacker cannot read data or execute code, but can make players show content under the wrong conditions. Exploitation additionally depends on Schedule Criteria being configured on the CMS; without criteria in use there is nothing meaningful to push.
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:N/I:L/A:N
Network-reachable endpoint with low complexity but needs a logged-in CMS user (PR:L); only playback/scheduling integrity is affected (I:L), with no confidentiality or availability impact.
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 authorization on POST /displaygroup/criteria/{displayGroupId} allows an authenticated user to send criteria updates to any display via XMR. These criteria determine schedule changes and can alter playback, for example by causing content scheduled for rainy weather to play when it is not raining. Exploitation requires Schedule Criteria to be in use on the CMS. 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
An authenticated user with standard Notification Centre access in Xibo CMS before 4.4.3 can download notification attach
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
EUVD-2026-112141
NVD
CVE.org
GitHub
Exploit-DB