CVE-2023-33178
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 · uneditedXibo is a content management system (CMS). An SQL injection vulnerability was discovered in the `/dataset/data/{id}` API route inside the CMS starting in version 1.4.0 and prior to versions 2.3.17 and 3.3.5. This allows an authenticated user to exfiltrate data from the Xibo database by injecting specially crafted values in to the `filter` parameter. Values allowed in the filter parameter are checked against a deny list of commands that should not be allowed, however this checking was done in a case sensitive manor and so it is possible to bypass these checks by using unusual case combinations. Users should upgrade to version 2.3.17 or 3.3.5, which fix this issue. There are no 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 confidenceSQL injection vulnerability in Xibo CMS where the `/dataset/data/{id}` API route's `filter` parameter is validated against a case-sensitive deny list. An authenticated attacker can bypass the filter by using unusual case combinations (e.g., 'UNion' instead of 'UNION') to inject SQL commands and exfiltrate database contents.
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>= 1.4.0, < 2.3.17>= 3.0.0, < 3.3.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine Xibo CMS versionLocate the version file or check the admin interface (typically under Admin > About) for the installed Xibo version numberAffected if Version is >= 1.4.0 and < 2.3.17, or >= 3.0.0 and < 3.3.5
-
Confirm dataset module is activeVerify that the DataSet feature is enabled in the Xibo installation - check via admin panel under Modules or Features, or check for the /dataset/data endpoint respondingAffected if DataSet module is enabled and accessible to authenticated users
-
Verify authentication requirements for the endpointAttempt to access the /dataset/data/{id} API route - the vulnerability requires an authenticated attacker, so confirm whether user authentication is required and enforcedAffected if The endpoint accepts authenticated requests and the filter parameter is processed
-
Inspect filter parameter validation logicReview the codebase for the deny list implementation in the filter validation routine for /dataset/data/{id} - look for case-sensitive SQL keyword blockingAffected if The filter validation uses a case-sensitive deny list that can be bypassed with case variants like 'UNion' or 'SelEct'
If Xibo CMS version falls within the affected ranges AND the DataSet module is enabled AND the /dataset/data endpoint processes filter parameters without case-insensitive validation, the environment is vulnerable to CVE-2023-33178.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.3.173.3.5
Upgrade to Xibo CMS version 2.3.17 or 3.3.5 to patch the vulnerability. No workarounds exist; the case-sensitive filter validation cannot be practically hardened without upgrading.
2.3.17 (for 1.x/2.x branches) or 3.3.5 (for 3.x branch)
- 1. Identify your current Xibo installation version by checking the admin panel or the version file in your installation directory
- 2. Determine which upgrade path applies: if you are on version 1.x or 2.x, upgrade to 2.3.17; if you are on version 3.x, upgrade to 3.3.5
- 3. Back up your existing Xibo database and files before proceeding with the upgrade
- 4. Download the appropriate fixed release (2.3.17 or 3.3.5) from the official Xibo repository (github.com/xibosignage/xibo)
- 5. Follow the standard Xibo upgrade instructions for your specific version, which typically involve replacing the application files and running any database migrations
- 6. After upgrade, verify the installation by logging into the CMS admin panel
- 7. Test the `/dataset/data/{id}` API route to confirm the fix is applied and the filter parameter is now properly sanitized (case-insensitive validation)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33178 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-33178 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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