dbcve.org
XiboApplication · Xibosignage

CVE-2023-33180

MEDIUM · 6.5 CVSS v3.1 Published 2023-05-30
Fix available
A fix is available. Upgrade to 3.3.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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 a content management system (CMS). An SQL injection vulnerability was discovered starting in version 3.2.0 and prior to version 3.3.2 in the `/display/map` API route inside the CMS. This allows an authenticated user to exfiltrate data from the Xibo database by injecting specially crafted values in to the `bounds` parameter. Users should upgrade to version 3.3.5, which fixes this issue. There are no known workarounds aside from upgrading.

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

SQL injection vulnerability in Xibo CMS versions 3.2.0 through 3.3.1 affecting the `/display/map` API route. An authenticated user can inject malicious SQL through the `bounds` parameter to exfiltrate data from the database.

MitigationUpgrade Xibo CMS to version 3.3.5 or later to resolve the SQL injection vulnerability. No workarounds are available; upgrading is the only remediation path.

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:>= 3.2.0, < 3.3.5

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
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 installation
    Locate the Xibo installation directory and check for version.php or similar version files. Common paths include /var/www/xibo or the web root if Xibo was deployed there. Check the admin panel footer or the version info in the CMS settings.
    Affected if The installed Xibo CMS version is 3.2.0 through 3.3.4 inclusive (versions prior to 3.3.5)
  2. Verify the affected API endpoint exists
    Check if the Xibo web application exposes the /display/map route. This is typically found in the routing configuration or by attempting to access the endpoint with valid authentication credentials.
    Affected if The /display/map endpoint is accessible and responds to requests
  3. Confirm authentication is enabled
    Review the Xibo authentication configuration to ensure user authentication is required for API access. Check if anonymous access is permitted to the /display/map route in the security settings.
    Affected if The /display/map endpoint can be accessed with authenticated user credentials
  4. Check for the vulnerable bounds parameter
    Examine the API request handling code for the /display/map route. Look for how the 'bounds' parameter is processed and whether it is used directly in database queries without proper parameterization.
    Affected if The bounds parameter is accepted and used in SQL queries without sanitization

A user is affected if their Xibo CMS installation is version 3.2.0 through 3.3.4 and the /display/map endpoint with the vulnerable bounds parameter is accessible to authenticated users.

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 3.3.5 or later
Fixed in 3.3.5
Interim mitigation

Upgrade Xibo CMS to version 3.3.5 or later to resolve the SQL injection vulnerability. No workarounds are available; upgrading is the only remediation path.

Recommended fix High confidence

Xibo CMS 3.3.5

  1. Backup your current Xibo CMS database and files before proceeding with the upgrade
  2. Download Xibo CMS version 3.3.5 from the official Xibo download page at xibosignage.com
  3. Follow the official Xibo upgrade documentation to apply the update to your existing installation
  4. After upgrade, verify the version number in the CMS admin panel matches 3.3.5
  5. Test the `/display/map` API endpoint to confirm the vulnerability is resolved
Caveat Review the Xibo 3.3.5 release notes for any breaking changes or required migration steps before upgrading

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

Fix this in Xibo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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