CVE
Xibo Signage Xibo CMS unauthorized access to DataSet RSS feeds
Affects Xibo CMS versions before 4.5.3 for users who hold dataset.modify permission and at least one editable dataset. Fixed in 4.5.3.
Written by a model from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 4.5.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Xibo CMS versions before 4.5.3 Attacker holds dataset.modify permission and a single editable dataset
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 27/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Xibo CMS, the digital signage management software, has an insecure direct object reference flaw in its RSS feed handling, affecting versions before 4.5.3. An attacker who can log in with the dataset.modify permission can reach other DataSets' RSS feeds remotely, then read, change, or delete them, steal their keys, and use those keys to pull DataSet data from victims.
Original description
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.
Who should check
Teams running Xibo CMS before 4.5.3 that grant dataset.modify permission to users
“Any user holding dataset.modify and a single editable dataset”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Packagist packages
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Xibo CMS versions before 4.5.3 Attacker holds dataset.modify permission and a single editable datasetUpgrade to a fixed version: 4.5.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130584 (Xibo CMS before 4.5.3 IDOR via /dataset/{id}/rss/{rssId}), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130584 (entry last updated 2026-11-17):
Affected:
- Packagist package xibosignage/xibo-cms: fixed in 4.5.3
Fixed versions: 4.5.3.
Conditions (all must be true for the bug to be hit):
- Xibo CMS versions before 4.5.3 (source: https://www.vulncheck.com/advisories/xibo-cms-before-4.5.3-idor-via-dataset-id-rss-rssid)
- Attacker holds dataset.modify permission and a single editable dataset (source: https://github.com/xibosignage/xibo-cms/security/advisories/GHSA-6482-4m2h-rjg6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-130584 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130584 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (Packagist): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/xibosignage/xibo-cms/security/advisories/GHSA-6482-4m2h-rjg6
- https://github.com/xibosignage/xibo-cms/commit/fce3bb318cbd1e0a9ff07555576d880a920b3a10
- https://github.com/xibosignage/xibo-cms/releases/tag/4.5.3
- https://github.com/xibosignage/xibo-cms/blob/4.5.2/lib/Controller/DataSetRss.php#L215-L218
- https://www.vulncheck.com/advisories/xibo-cms-before-4.5.3-idor-via-dataset-id-rss-rssid
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130584
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130584"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- xibosignage/xibo-cmsPackagist
fixed in 4.5.3
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130584
Is CVE-2026-130584 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The /dataset/{id}/rss/{rssId} endpoint does not properly check which DataSet an RSS feed belongs to. This lets a user with dataset.modify and one editable dataset read, edit, or delete other DataSets' RSS feeds, steal their feed PSKs, and read rows from other datasets.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-130584?
xibosignage/xibo-cms (Packagist): before 4.5.3.Source: cve.now feed data
Am I affected, and how do I check?
Xibo CMS versions before 4.5.3 are affected. The relevant setup is an account holding dataset.modify permission with a single editable dataset. Check the installed CMS version and which user roles hold dataset.modify to see whether this setup applies.Source: vulncheck.com, github.com
How do I fix CVE-2026-130584?
Upgrade Xibo CMS to 4.5.3 or later, the version the product range lists as fixed.Source: vulncheck.com, github.com
Why do the sources disagree?
The description says the data can be exfiltrated without authentication, while the CVSS vector records low privileges required (PR:L). The description's account is the impact side, and the vector's PR:L reflects that an account with dataset.modify and an editable dataset is needed.Source: vulncheck.com, github.com