VulnerabilityPublished 12 May 2026

CVE-2026-42141: xibosignage xibo-cms · Server-Side Request Forgery (SSRF)

Affects xibosignage xibo-cmsSource CVE Database V5

Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 4.4.1 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

7.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.4.1

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade xibo-cms and xibosignage/xibo-cms to 4.4.1.

Affected software

Product	Affected	Fixed in
xibosignagexibo-cms	Affected <4.4.1	Fixed in 4.4.1
GitHubxibosignage/xibo-cms`pkg:github/xibosignage/xibo-cms`Other threats	Affected <4.4.1	Fixed in 4.4.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Xibo CMS version 4.4.1. Since this is a cloud-hosted service, the vendor manages remediation server-side. Users should verify with the vendor advisory that their instance is updated to 4.4.1 or later to ensure this vulnerability is mitigated.

Description

CVE-2026-42141 is a Server-Side Request Forgery (SSRF) vulnerability in the Xibo CMS digital signage platform prior to version 4.4.1. Authenticated users with Library upload permissions can exploit this flaw to make arbitrary HTTP requests from the CMS server to internal or external network resources. This can lead to scanning internal infrastructure, accessing cloud metadata endpoints such as AWS IMDS, interacting with unauthenticated internal services, or exfiltrating data. The vulnerability has a high severity with a CVSS score of 7.7 and is fixed in version 4.4.1. The vendor manages remediation for this cloud-hosted service.

Impact

Successful exploitation allows an authenticated user with limited permissions to perform SSRF attacks, potentially leading to internal network reconnaissance, unauthorized access to cloud metadata services (e.g., AWS IMDS), interaction with internal services without authentication, and data exfiltration. This compromises confidentiality but does not affect integrity or availability according to the CVSS vector.

Summary

Xibo CMS versions before 4.4.1 contain an authenticated SSRF vulnerability (CWE-918) that allows users with Library upload permissions to induce the server to send arbitrary HTTP requests. This can be leveraged to probe internal networks, access sensitive cloud metadata endpoints, and interact with internal services lacking authentication. The vulnerability is addressed in version 4.4.1. Since Xibo CMS is a cloud service, the vendor typically handles patching server-side.

CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/xibosignage/xibo-cms/security/advisories/GHSA-fwq8-c4gw-pxmh (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 May 2026, 18:44 UTC

Public exploits and detectionGitHub proofs of concept

WeaknessesCWE-918

Technical details

References

Community reviews

Related threats