CVE-2026-50541: missing authz on dataset CSV export

CISO Take

Xibo is an open source digital signage CMS, and before version 4.4.3 the dataset CSV export endpoint (GET /dataset/export/csv/{id}) lacks an access-control check (CWE-862), so an authenticated user can export any dataset, including administrator-created ones, by iterating sequential IDs. This is a low-severity-in-practice issue for AI/ML estates: it has a CVSS of 6.5, no EPSS score, no KEV listing, no public exploit and no Nuclei template, and it requires a non-default privilege to edit and delete all DataSets. The tracked AI category (ml_data) is a loose fit, since this is a general digital signage product with no listed AI packages or downstream dependents. Organizations running Xibo should upgrade to 4.4.3 or later (or the 4.5.0-beta), review who holds the all-DataSets edit privilege, and check access logs for sequential requests to the export endpoint.

Sources:NVDGitHub AdvisoryATLAS

What is the risk?

Medium. The attack is network-reachable with low complexity and no user interaction, but it needs an authenticated account that holds the privilege to edit and delete all DataSets, which is not granted to non-administrators by default. The impact is confidentiality only (C:H, I:N, A:N). There is no known exploitation, EPSS data or public PoC. The practical risk depends on how sensitive the data stored in Xibo datasets is and how many users have been given this privilege.

How does the attack unfold?

Initial Access

Attacker logs in with a valid CMS account that holds the edit-all-DataSets privilege.

AML.T0012

Enumeration

Attacker iterates over sequential dataset IDs against the CSV export endpoint.

AML.T0036

Exploitation

The missing access-control check lets the export succeed for datasets created by administrators.

AML.T0049

Impact

Attacker exfiltrates the dataset contents as CSV, exposing confidential business data.

AML.T0025

Initial Access

Attacker logs in with a valid CMS account that holds the edit-all-DataSets privilege.

AML.T0012

Enumeration

Attacker iterates over sequential dataset IDs against the CSV export endpoint.

AML.T0036

Exploitation

The missing access-control check lets the export succeed for datasets created by administrators.

AML.T0049

Impact

Attacker exfiltrates the dataset contents as CSV, exposing confidential business data.

AML.T0025

How severe is it?

CVSS 3.1

6.5 / 10

EPSS

0.4%

chance of exploitation in 30 days

Higher than 31% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AVNetwork

ACLow

PRLow

UINone

SUnchanged

CHigh

INone

ANone

What should I do?

1 step

1) Upgrade Xibo CMS to 4.4.3 or later (the fix is also in 4.5.0-beta). 2) Audit which users hold the privilege to edit and delete all DataSets independently of Layouts, and remove it where it is not needed. 3) Review web server and CMS logs for GET /dataset/export/csv/{id} requests that iterate over sequential IDs or come from unexpected accounts. 4) Do not store sensitive or regulated data in datasets until patched. 5) Rotate any credentials or secrets that may have been placed in dataset content.

How is it classified?

Data LeakageAuth BypassFrameworkAML.T0025- Exfiltration via Cyber Means AML.T0036- Data from Information Repositories

Which compliance frameworks are affected?

This CVE is relevant to:

ISO 42001

A.7.2-Data for development and enhancement of AI systems

NIST AI RMF

MANAGE 2.3-Mechanisms to respond to and recover from unknown risks

OWASP LLM Top 10

LLM02-Sensitive Information Disclosure

Frequently Asked Questions

What is CVE-2026-50541?

Xibo is an open source digital signage CMS, and before version 4.4.3 the dataset CSV export endpoint (GET /dataset/export/csv/{id}) lacks an access-control check (CWE-862), so an authenticated user can export any dataset, including administrator-created ones, by iterating sequential IDs. This is a low-severity-in-practice issue for AI/ML estates: it has a CVSS of 6.5, no EPSS score, no KEV listing, no public exploit and no Nuclei template, and it requires a non-default privilege to edit and delete all DataSets. The tracked AI category (ml_data) is a loose fit, since this is a general digital signage product with no listed AI packages or downstream dependents. Organizations running Xibo should upgrade to 4.4.3 or later (or the 4.5.0-beta), review who holds the all-DataSets edit privilege, and check access logs for sequential requests to the export endpoint.

Is CVE-2026-50541 actively exploited?

No confirmed active exploitation of CVE-2026-50541 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-50541?

1) Upgrade Xibo CMS to 4.4.3 or later (the fix is also in 4.5.0-beta). 2) Audit which users hold the privilege to edit and delete all DataSets independently of Layouts, and remove it where it is not needed. 3) Review web server and CMS logs for GET /dataset/export/csv/{id} requests that iterate over sequential IDs or come from unexpected accounts. 4) Do not store sensitive or regulated data in datasets until patched. 5) Rotate any credentials or secrets that may have been placed in dataset content.

What systems are affected by CVE-2026-50541?

This vulnerability affects the following AI/ML architecture patterns: Digital signage content management, Data feed and dataset integrations, Analytics output display pipelines.

What is the CVSS score for CVE-2026-50541?

CVE-2026-50541 has a CVSS v3.1 base score of 6.5 (MEDIUM). The EPSS exploitation probability is 0.37%.

What is the AI security impact?

Affected AI Architectures

Digital signage content managementData feed and dataset integrationsAnalytics output display pipelines

MITRE ATLAS Techniques

AML.T0025Exfiltration via Cyber Means

AML.T0036Data from Information Repositories

Compliance Controls Affected

ISO 42001: A.7.2

NIST AI RMF: MANAGE 2.3

OWASP LLM Top 10: LLM02

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An adversary, or a malicious insider, holds a CMS account that has been granted the privilege to edit all DataSets. They script requests to GET /dataset/export/csv/1, /2, /3 and so on. Because the endpoint does not check ownership or permission on each dataset, they download CSV exports of datasets created by administrators. They then collect any business data, analytics feeds or ML-derived outputs stored there.

Weaknesses (CWE)

CWE-862Missing AuthorizationPrimary CWE-862Missing Authorization

CWE-862 — Missing Authorization: The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

[Architecture and Design] Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
[Architecture and Design] Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Source: MITRE CWE corpus.