# CVE-2026-42141: Xibo: Authenticated Server-Side Request Forgery (SSRF) in Library Upload via URL functionality

> Authenticated users with library upload permissions can perform server-side request forgery to access internal resources or cloud metadata.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **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:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-fwq8-c4gw-pxmh

## What is CVE-2026-42141?

CVE-2026-42141 is a high-severity server-side request forgery vulnerability in xibosignage xibo-cms, published on 12 May 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. Prior to 4.4.1, an authenticated Server-Side Request Forgery (SSRF) vulnerability in the Xibo CMS allows users with Library upload 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. This vulnerability is fixed in 4.4.1.

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

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


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

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

## Is CVE-2026-42141 being exploited?

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

Public exploit code:

- SSRF vulnerability in Xibo CMS (CVE-2026-42141) (github_poc): https://github.com/H4zaz/CVE-2026-42141-xibo-ssrf

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42141 is a high-severity server-side request forgery vulnerability in xibosignage xibo-cms, published on 12 May 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-42141 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-42141/ (Markdown: https://insights.sbomify.com/CVE-2026-42141/index.md)
```

## Sources

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

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