CVE-2026-130584: Xibo CMS: IDOR in DataSet RSS leaks other tenants' data

HIGH
Published November 17, 2026
CISO Take

Xibo CMS before 4.5.3 has an insecure direct object reference in its DataSet RSS feed handling: an authenticated user with dataset.modify permission can pair their own DataSet id with another DataSet's RSS id to read, edit or delete that feed and steal its pre-shared key (PSK). The PSK unlocks the unauthenticated /rss/{psk} endpoint, so an attacker can then pull the victim DataSet's rows without any further authentication. The CVSS score is 8.3 (high) and it is network-reachable with low complexity, but there is no EPSS score, no KEV listing, no public exploit and no Nuclei template, so mass exploitation is not currently evidenced. The AI relevance is marginal, limited to cases where Xibo DataSets feed analytics or ML data pipelines. Upgrade to Xibo CMS 4.5.3, rotate any RSS PSKs that may have been exposed, and review who holds dataset.modify permission.

Sources:NVDGitHub AdvisoryVulnCheckATLAS

What is the risk?

High severity (CVSS 8.3) driven by network access, low complexity, low privileges and no user interaction, with high confidentiality and integrity impact and low availability impact. Exploitation requires a valid account with dataset.modify, which limits the attacker pool to insiders or compromised low-privilege accounts. There is no known active exploitation, no public exploit and no EPSS data. Likelihood is moderate and impact is high for multi-tenant or shared Xibo deployments. Direct AI/ML risk is low because Xibo is a digital signage CMS, not an AI platform.

How does the attack unfold?

Initial Access
Attacker authenticates with a low-privilege account holding dataset.modify.
AML.T0012
Exploitation
Attacker pairs their own DataSet id with a foreign RSS id to bypass the ownership check and obtain the victim feed's PSK.
AML.T0049
Collection and Exfiltration
Attacker uses the PSK against the unauthenticated /rss/{psk} endpoint to download the victim DataSet rows.
AML.T0025
Impact
Attacker edits or deletes feeds, tampering with or disrupting downstream data consumers.
AML.T0036

How severe is it?

CVSS 3.1
8.3 / 10
EPSS
N/A
Exploitation Status
No known exploitation
Sophistication
Trivial

What is the attack surface?

AVACPRUISCIA
AVNetwork
ACLow
PRLow
UINone
SUnchanged
CHigh
IHigh
ALow

What should I do?

1 step
  1. 1) Upgrade Xibo CMS to 4.5.3 or later (fix commit fce3bb3). 2) Rotate PSKs for all DataSet RSS feeds and re-issue them to legitimate consumers. 3) Audit and minimize dataset.modify permissions and review accounts for compromise. 4) Review web and access logs for requests to the DataSetRss controller that mix mismatched DataSet and RSS ids, and for unusual access to /rss/{psk} from unfamiliar IPs. 5) Restrict the /rss/ endpoint at the reverse proxy or WAF to known consumers where feasible. 6) Verify DataSet contents for unauthorized edits or deleted feeds.

How is it classified?

Which compliance frameworks are affected?

This CVE is relevant to:

EU AI Act
Art. 15-Accuracy, robustness and cybersecurity
ISO 42001
A.7.4-Quality of data for AI systems
NIST AI RMF
MANAGE 2.3-Respond to previously unknown risks and manage identified vulnerabilities

Frequently Asked Questions

What is CVE-2026-130584?

Xibo CMS before 4.5.3 has an insecure direct object reference in its DataSet RSS feed handling: an authenticated user with dataset.modify permission can pair their own DataSet id with another DataSet's RSS id to read, edit or delete that feed and steal its pre-shared key (PSK). The PSK unlocks the unauthenticated /rss/{psk} endpoint, so an attacker can then pull the victim DataSet's rows without any further authentication. The CVSS score is 8.3 (high) and it is network-reachable with low complexity, but there is no EPSS score, no KEV listing, no public exploit and no Nuclei template, so mass exploitation is not currently evidenced. The AI relevance is marginal, limited to cases where Xibo DataSets feed analytics or ML data pipelines. Upgrade to Xibo CMS 4.5.3, rotate any RSS PSKs that may have been exposed, and review who holds dataset.modify permission.

Is CVE-2026-130584 actively exploited?

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

How to fix CVE-2026-130584?

1) Upgrade Xibo CMS to 4.5.3 or later (fix commit fce3bb3). 2) Rotate PSKs for all DataSet RSS feeds and re-issue them to legitimate consumers. 3) Audit and minimize dataset.modify permissions and review accounts for compromise. 4) Review web and access logs for requests to the DataSetRss controller that mix mismatched DataSet and RSS ids, and for unusual access to /rss/{psk} from unfamiliar IPs. 5) Restrict the /rss/ endpoint at the reverse proxy or WAF to known consumers where feasible. 6) Verify DataSet contents for unauthorized edits or deleted feeds.

What systems are affected by CVE-2026-130584?

This vulnerability affects the following AI/ML architecture patterns: data pipelines, multi-tenant content management systems, dataset/feed distribution services.

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

CVE-2026-130584 has a CVSS v3.1 base score of 8.3 (HIGH).

What is the AI security impact?

Affected AI Architectures

data pipelinesmulti-tenant content management systemsdataset/feed distribution services

MITRE ATLAS Techniques

AML.T0012Valid Accounts
AML.T0025Exfiltration via Cyber Means
AML.T0036Data from Information Repositories

Compliance Controls Affected

EU AI Act: Art. 15
ISO 42001: A.7.4
NIST AI RMF: MANAGE 2.3

What are the technical details?

Original Advisory

Xibo CMS before 4.5.3 contains an insecure direct object reference vulnerability that allows authenticated users to access other DataSets' RSS feeds by pairing their own DataSet id with a foreign RSS id. Attackers with dataset.modify permission can read, edit, or delete feeds and steal PSKs, then use the unauthenticated /rss/{psk} endpoint to exfiltrate victim DataSet rows.

Exploitation Scenario

An attacker holds a low-privilege Xibo account with dataset.modify on their own DataSet. They call the DataSet RSS edit endpoint with their own DataSet id and a foreign RSS id, which the vulnerable code does not check for ownership. The response exposes the victim feed's PSK, and the attacker then requests /rss/{psk} without authentication to download all rows from the victim DataSet. If that DataSet feeds an analytics or ML pipeline, the attacker can also edit the feed to inject manipulated data or delete it to disrupt the pipeline.

Weaknesses (CWE)

CWE-639 — Authorization Bypass Through User-Controlled Key: The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

  • [Architecture and Design] For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
  • [Architecture and Design, Implementation] Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.

Source: MITRE CWE corpus.

CVSS Vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L

Timeline

Published
November 17, 2026
Last Modified
November 17, 2026
First Seen
November 17, 2026

Related Vulnerabilities