# CVE-2024-41944: Sensitive Information Disclosure abusing SQL Injection in Xibo CMS proof of play report

> Authenticated attackers can inject SQL into the proof of play report API to read and modify arbitrary database data in Xibo CMS.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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:** 30 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-v6q4-h869-gm3r

## What is CVE-2024-41944?

CVE-2024-41944 is a medium-severity SQL injection vulnerability in xibosignage xibo-cms, published on 30 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Xibo is a content management system (CMS). An SQL injection vulnerability was discovered in the `report/data/proofofplayReport` API route inside the CMS. This allows an authenticated user to to obtain and modify arbitrary data from the Xibo database by injecting specially crafted values in to the `sortBy` parameter. Users should upgrade to version 3.3.12 or 4.0.14 which fix this issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-41944?


## How do I fix CVE-2024-41944?

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

## Is CVE-2024-41944 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41944 and fix it if it is affected.

What it is: CVE-2024-41944 is a medium-severity SQL injection vulnerability in xibosignage xibo-cms, published on 30 Jul 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41944 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-2024-41944/ (Markdown: https://insights.sbomify.com/CVE-2024-41944/index.md)
```

## Sources

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

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