# CVE-2026-31955: Xibo CMS has Authenticated Server-Side Request Forgery (SSRF) in Remote DataSet Functionality

> Authenticated users with DataSet permissions can perform Server-Side Request Forgery to access internal resources or cloud metadata.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 25 Apr 2026
- **Also known as:** GHSA-5q58-9vhx-xg2p

## What is CVE-2026-31955?

CVE-2026-31955 is a medium-severity server-side request forgery vulnerability in xibosignage xibo-cms, published on 24 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Xibo is an open source digital signage platform with a web content management system and Windows display player software. An authenticated Server-Side Request Forgery (SSRF) vulnerability in versions prior to 4.4.1 allows users with DataSet permissions to make arbitrary HTTP requests from the CMS server to internal or external network resources. This can be exploited to scan internal infrastructure, access local cloud metadata endpoints (e.g., AWS IMDS), interact with internal services that lack authentication, or exfiltrate data. Exploitation of the vulnerability is possible on behalf of an authorized user who has both of the following privileges, which are not granted to non-admins as standard: Include "Add DataSet" button to allow for additional DataSets to be created independently to Layouts. Users should upgrade to version 4.4.1 which fixes this issue. Upgrading to a fixed version is necessary to remediate. Users unable to upgrade should revoke such privileges from users they do not trust.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Xibosignage Xibo.

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

No fix has been published for CVE-2026-31955 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31955 being exploited?

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

## Other vulnerabilities in xibosignage xibo-cms

- [CVE-2023-33177](https://insights.sbomify.com/CVE-2023-33177/): Xibo CMS vulnerable to Remote Code Execution through Zip Slip (high 8.8)
- [CVE-2024-41802](https://insights.sbomify.com/CVE-2024-41802/): Xibo allows Sensitive Information Disclosure abusing SQL Injection in Xibo CMS DataSet Data Import (high 8.1)
- [CVE-2026-31952](https://insights.sbomify.com/CVE-2026-31952/): Xibo CMS API has SQL Injection via DataSet Filter Parameter (high 7.6)
- [CVE-2013-4887](https://insights.sbomify.com/CVE-2013-4887/): SQL injection in n/a (high 7.5)
- [CVE-2025-62369](https://insights.sbomify.com/CVE-2025-62369/): Xibo CMS: Remote Code Execution through module templates (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31955 is a medium-severity server-side request forgery vulnerability in xibosignage xibo-cms, published on 24 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31955 in the wild and no public exploit code.

Affected product: xibosignage xibo-cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-31955/ (Markdown: https://insights.sbomify.com/CVE-2026-31955/index.md)
```

## Sources

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

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