dbcve.org
XiboApplication · Xibosignage

CVE-2026-31953

MEDIUM · 5.4 CVSS v3.1 Published 2026-04-24
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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. A stored Cross-Site Scripting (XSS) vulnerability in versions prior to 4.4.1 allows an authenticated user with notification creation permissions to inject arbitrary JavaScript into the notification body. When the notification is set as an "interrupt," the payload executes automatically in the browser of any targeted user upon login, requiring zero user interaction. Exploitation of the vulnerability is possible on behalf of an authorized user who has both of the following privileges, which are not granted to non-admins as standard: Access to the Notification Centre to view past notifications, and include "Add Notification" button to allow for the creation of new notifications. Users should upgrade to version 4.4.1 which fixes this issue. Upgrading to a fixed version is necessary to remediate. Users unable to upgrade should revoke such privileges from users they do not trust.

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

A stored Cross-Site Scripting (XSS) vulnerability in Xibo CMS versions prior to 4.4.1 allows authenticated users with notification creation privileges to inject arbitrary JavaScript into notification bodies. When notifications are configured as 'interrupt' type, the malicious payload executes automatically in the browser of any user upon login without requiring any user interaction.

MitigationUpgrade to Xibo version 4.4.1 or later. If upgrading is not feasible, revoke notification creation privileges from untrusted users until the upgrade can be performed.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XiboApplication
Affected:< 4.4.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Xibo installation and check the version number (typically found in the CMS admin interface under About or in configuration files)
    Affected if The installed version is lower than 4.4.1 (e.g., 4.4.0, 4.3.x, earlier versions)
  2. Verify user notification privileges
    Check if any user accounts in the system have notification creation privileges. This is typically found in the User Group permissions or User settings within the Xibo admin panel
    Affected if Authenticated users with notification creation privileges exist in the system
  3. Inspect existing notifications for interrupt type
    Access the Notifications section in the Xibo admin panel or query the database for records in the notification table where the type or interrupt flag is set to trigger on login
    Affected if Any notifications are configured as interrupt type that execute automatically upon user login
  4. Review notification content for suspicious patterns
    Examine the body content of interrupt-type notifications for potential XSS payloads (e.g., script tags, event handlers, javascript: URIs)
    Affected if Interrupt-type notifications contain unsanitized HTML or script tags in their body content

You are affected if running Xibo CMS versions prior to 4.4.1 and your system either has users with notification creation privileges or contains existing interrupt-type notifications that could carry malicious payloads.

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
Upgrade available Upgrade to 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Upgrade to Xibo version 4.4.1 or later. If upgrading is not feasible, revoke notification creation privileges from untrusted users until the upgrade can be performed.

Recommended fix High confidence

4.4.1

  1. Backup the current Xibo installation and database before proceeding with the upgrade
  2. Download Xibo version 4.4.1 from the official repository or release channels
  3. Follow the official Xibo upgrade documentation for your deployment method (manual or package-based)
  4. Verify that the upgrade completed successfully by checking the version number in the admin interface
  5. Log in as an administrator and confirm the notification functionality works correctly
  6. Clear any cached data if applicable to ensure the new version is fully loaded

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

Fix this in Xibo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-31953 — 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-31953 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