# CVE-2023-33181: Sensitive Information Disclosure abusing Stack Trace in Xibo CMS

> Attackers can obtain sensitive server path information via stack traces in Xibo CMS API routes when invalid parameters are provided.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2023
- **Updated:** 9 Jan 2025
- **Also known as:** GHSA-c9cx-ghwr-x58m

## What is CVE-2023-33181?

CVE-2023-33181 is a medium-severity vulnerability in xibosignage xibo-cms, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Xibo is a content management system (CMS). Starting in version 3.0.0 and prior to version 3.3.5, some API routes will print a stack trace when called with missing or invalid parameters revealing sensitive information about the locations of paths that the server is using. Users should upgrade to version 3.3.5, which fixes this issue. There are no known workarounds aside from upgrading.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

## Which versions are affected by CVE-2023-33181?

It affects 1 product.


Products: Xibosignage Xibo.

## How do I fix CVE-2023-33181?

No fix has been published for CVE-2023-33181 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-33181 being exploited?

There is no known exploitation of CVE-2023-33181 in the wild and no public exploit code.

## Other vulnerabilities in xibosignage xibo-cms

- [CVE-2023-33177](https://insights.sbomify.com/CVE-2023-33177/): Xibo CMS vulnerable to Remote Code Execution through Zip Slip (high 8.8)
- [CVE-2024-41802](https://insights.sbomify.com/CVE-2024-41802/): Xibo allows Sensitive Information Disclosure abusing SQL Injection in Xibo CMS DataSet Data Import (high 8.1)
- [CVE-2026-31952](https://insights.sbomify.com/CVE-2026-31952/): Xibo CMS API has SQL Injection via DataSet Filter Parameter (high 7.6)
- [CVE-2013-4887](https://insights.sbomify.com/CVE-2013-4887/): SQL injection in n/a (high 7.5)
- [CVE-2025-62369](https://insights.sbomify.com/CVE-2025-62369/): Xibo CMS: Remote Code Execution through module templates (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-33181 and fix it if it is affected.

What it is: CVE-2023-33181 is a medium-severity vulnerability in xibosignage xibo-cms, published on 30 May 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-33181 in the wild and no public exploit code.

Affected product: xibosignage xibo-cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-33181/ (Markdown: https://insights.sbomify.com/CVE-2023-33181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-33181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-33181
- OSV: https://osv.dev/vulnerability/CVE-2023-33181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-33181/
Summaries are generated and may contain mistakes; the official description above is the record.
