# CVE-2026-31952: Xibo CMS API has SQL Injection via DataSet Filter Parameter

> Authenticated users with specific privileges can inject SQL into the DataSet filter parameter to read and modify arbitrary database data.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-rq92-f6fv-3629

## What is CVE-2026-31952?

CVE-2026-31952 is a high-severity SQL injection vulnerability in xibosignage xibo-cms, published on 24 Apr 2026. Any signed-in user can exploit it over the network, 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. Versions 1.7 through 4.4.0 have an SQL injection vulnerability in the API routes inside the CMS responsible for Filtering DataSets. This allows an authenticated user to to obtain and modify arbitrary data from the Xibo database by injecting specially crafted values in to the API filter parameter. Exploitation of the vulnerability is possible on behalf of an authorized user who has either of the `Access to DataSet Feature` privilege or the `Access to the Layout Feature` privilege. Users should upgrade to version 4.4.1 which fixes this issue. Customers who host their CMS with Xibo Signage have been patched if they are using 4.4, 4.3, 3.3, 2.3 or 1.8. Upgrading to a fixed version is necessary to remediate. Patches are available for earlier versions of Xibo CMS that are out of support, namely 3.3, 2.3, and 1.8.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-184 (Incomplete List of Disallowed Inputs)

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

It affects 1 product.


Products: Xibosignage Xibo.

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

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

## Is CVE-2026-31952 being exploited?

There is no known exploitation of CVE-2026-31952 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-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)
- [CVE-2013-4889](https://insights.sbomify.com/CVE-2013-4889/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31952 is a high-severity SQL injection vulnerability in xibosignage xibo-cms, published on 24 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-31952 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-31952/ (Markdown: https://insights.sbomify.com/CVE-2026-31952/index.md)
```

## Sources

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

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