Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as user with elevated DataSet privilege
-
ExploitEnumerate sequential dataset IDs
-
ExecutionRequest GET /dataset/export/csv/{id} per ID
-
ImpactExfiltrate administrator dataset contents as CSV
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 an authenticated CMS account AND the specific non-default privilege 'Allow edits including deletion to all created DataSets independently to Layouts,' which the vendor states is not granted to non-administrators as standard. With that privilege, the attacker reaches GET /dataset/export/csv/{id} over the network and iterates sequential dataset IDs to export datasets owned by others, including administrators. Limiting factors: the elevated privilege gate (near-admin, not available to ordinary users by default), the fact that impact is read-only disclosure of dataset contents (no integrity/availability effect), and that only deployments on version 4.4.2 or earlier are affected (fixed in 4.4.3). |
| Impact | This is a moderate, authorization-scoped information-disclosure issue rather than a top-priority emergency. The input CVSS of 6.5 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) reflects network reachability with low complexity and no user interaction, but confidentiality-only impact (C:H, I:N, A:N) via missing object-level authorization (CWE-862). A key signal conflicts with the raw vector: although the vector encodes PR:L, the advisory states exploitation requires the privilege 'Allow edits including deletion to all created DataSets independently to Layouts,' which is explicitly NOT granted to non-administrators by default - so in practice the required privilege is near-administrative, which lowers real-world exploitability below what PR:L implies. No EPSS score, no CISA KEV listing, and no verified public exploit code were provided in the input; the only exploitation status we can assert is 'no public exploit identified at time of analysis.' The vuln.today decision label is 'this_month' (not act_now/emergency). Net: a real but non-urgent fix - prioritize patching within the month and audit who holds the elevated DataSet privilege, but this is not a widely-automatable, unauthenticated mass-exploitation scenario. |
| Exploit ScenarioDerived | An authenticated Xibo CMS user who has been granted the elevated 'edit/delete all DataSets independently of Layouts' privilege calls GET /dataset/export/csv/{id} while incrementing the numeric {id}, and because the endpoint performs no per-object access-control check (fixed by adding checkEditable), the server returns CSV exports of datasets the user was not meant to see, including administrator-created datasets. No public exploit code is identified in the sources, though the GHSA advisory and the fix PR diff publicly document the exact vulnerable endpoint and trigger. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Missing object-level authorization on the dataset CSV export endpoint in Xibo CMS 4.4.2 and earlier lets a privileged authenticated user export the contents of any dataset - including those created by administrators - by iterating over sequential dataset IDs. Reaching the endpoint (GET /dataset/export/csv/{id}) requires a CMS account holding the non-default privilege that allows edits, including deletion, to all created DataSets independently of Layouts, which the vendor states is not granted to non-administrators as standard; the result is read-only disclosure of data with no integrity or availability impact. The flaw is fixed in 4.4.3, and no public exploit code was identified at time of analysis, with the assessed severity moderated by the near-administrative privilege gate and the confidentiality-only impact.
RemediationAI
Vendor-released patch: upgrade to Xibo CMS 4.4.3, which adds the missing checkEditable() authorization check on the CSV export route (the fix is also contained in the 4.5.0-beta release). For deployments that cannot upgrade immediately, the vendor's stated workaround is to revoke the privilege 'Allow edits including deletion to all created DataSets independently to Layouts' from any user who is not fully trusted, which removes the precondition for exploitation at the cost of those users no longer being able to manage shared datasets; the advisory is explicit that upgrading is necessary to remediate and that this is the only mitigation it offers. After upgrading, review dataset contents for unexpected exposure and, if the privilege was broadly assigned, treat the affected data as disclosed. Reference advisory: https://github.com/xibosignage/xibo-cms/security/advisories/GHSA-v6xr-pmg9-qpmv.
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 is an open source digital signage platform consisting of a PHP web content management system (xibo-cms) and a Windows display player. The affected code is the DataSet controller (lib/Controller/DataSet.php, method exportToCsv), which serves GET /dataset/export/csv/{id} and streams a temporary CSV file built from a dataset's rows. The root cause is CWE-862, Missing Authorization: the handler performed no per-object access check before generating the export, so any session that could reach the route could request an arbitrary dataset ID. Because dataset identifiers are sequential, an attacker did not need to guess or leak an ID - a simple loop walked the range and pulled every dataset's contents. The upstream fix in pull request 3493 inserts a call to $this->getUser()->checkEditable($dataSet) before export and throws AccessDeniedException when the check fails, bringing the export path in line with the object-level permission model used elsewhere in the CMS; the same commit also reformats the temporary filename generation line. Exploitation by any ordinary authenticated user is not established, since the functional gate is the elevated DataSet-editing privilege, and the vulnerability type is a horizontal IDOR rather than an authentication bypass despite the reference tag.
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
Network, low-complexity, no UI; PR:H because the advisory requires an elevated non-default DataSet privilege; C:H for arbitrary dataset export, no integrity 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 access-control checks on GET /dataset/export/csv/{id} allow an authenticated user to export data from any dataset, including datasets created by administrators, by iterating over sequential dataset IDs. Exploitation requires access to the privilege allowing edits, including deletion, to all created DataSets independently of Layouts. This privilege is not 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
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 `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-112086
NVD
CVE.org
GitHub
Exploit-DB