dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2026-42141

HIGH · 7.7 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an authenticated Server-Side Request Forgery (SSRF) vulnerability in Xibo CMS versions prior to 4.4.1. Users with Library upload permissions can cause the CMS server to make arbitrary HTTP requests to internal or external network resources, enabling infrastructure scanning, cloud metadata access (e.g., AWS IMDS), and interaction with unauthenticated internal services.

MitigationUpgrade Xibo CMS to version 4.1.4 or later to patch the SSRF vulnerability. Additionally, restrict Library upload permissions to only trusted users and implement network segmentation to limit the impact of SSRF attacks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Xibo CMS version
    Locate the version file or admin panel. Check for a version.php file in the CMS root directory, or log into the admin panel and navigate to Settings > About to view the installed version number.
    Affected if The installed version is below 4.1.4 (for example, 4.0.0, 3.0.0, or any version prior to 4.1.4).
  2. Verify Library upload permission is assigned
    Log into the Xibo admin panel as an administrator. Navigate to Users > User Groups or Users > Users. Examine which users or groups have the Library upload permission enabled. This permission is typically found under the "Media" or "Library" permissions section for each user or group.
    Affected if Any user account has Library upload permissions enabled (this is the permission level required to trigger the SSRF flaw).
  3. Check for unauthorized outbound HTTP requests
    Review web server access logs (Apache, Nginx, or IIS logs depending on your setup) for requests originating from the CMS server to internal IP ranges (10.x.x.x, 192.168.x.x, 172.16-31.x.x) or cloud metadata endpoints (169.254.169.254). Look for unusual GET or POST requests to internal resources initiated by the CMS application.
    Affected if Log entries show HTTP requests from the CMS server to internal network addresses or cloud metadata services that were not initiated by legitimate administrator actions.

You are affected if your Xibo CMS version is below 4.1.4 AND any user account has Library upload permissions enabled, allowing an authenticated attacker to trigger arbitrary outbound HTTP requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Xibo CMS to version 4.1.4 or later to patch the SSRF vulnerability. Additionally, restrict Library upload permissions to only trusted users and implement network segmentation to limit the impact of SSRF attacks.

Recommended fix High confidence

4.4.1

  1. 1. Back up your Xibo CMS database and files before upgrading.
  2. 2. Download Xibo CMS version 4.4.1 from the official Xibo release repository or website.
  3. 3. Follow the standard Xibo upgrade instructions for your deployment method (Docker, manual install, etc.).
  4. 4. Verify the upgrade was successful by logging into the CMS.
  5. 5. Ensure the user role with Library upload permissions is still correctly configured as needed for your workflow.
Caveat Review release notes for 4.4.1 for any breaking changes or deprecations before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42141 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data