# CVE-2026-130584: Xibo CMS before 4.5.3 IDOR via /dataset/{id}/rss/{rssId}


- **Severity:** High 8.7 (`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 in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-6482-4m2h-rjg6, GHSA-gm2x-7c5c-pmr3

## What is CVE-2026-130584?

CVE-2026-130584 is a high-severity vulnerability in Xibo CMS, published on 17 Nov 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-130584?

1 open source package ship an affected version, including xibosignage/xibo-cms.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `xibosignage/xibo-cms` | Packagist | `pkg:composer/xibosignage/xibo-cms` | All versions | 4.5.3 |

## How do I fix CVE-2026-130584?

Upgrade xibosignage/xibo-cms to 4.5.3 or later.

## Is CVE-2026-130584 being exploited?

There is no known exploitation of CVE-2026-130584 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-130584 and fix it if it is affected.

What it is: CVE-2026-130584 is a high-severity vulnerability in Xibo CMS, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130584 in the wild and no public exploit code.

Affected packages and fixed versions:
- xibosignage/xibo-cms (Packagist): affected all versions; fixed in 4.5.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-130584/ (Markdown: https://insights.sbomify.com/CVE-2026-130584/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-130584
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-130584
- OSV: https://osv.dev/vulnerability/CVE-2026-130584

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-130584/
Summaries are generated and may contain mistakes; the official description above is the record.
