# CVE-2023-33177: Xibo CMS vulnerable to Remote Code Execution through Zip Slip

> Authenticated attackers can upload malicious zip files to achieve remote code execution via path traversal in Xibo CMS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 17 Jun 2025
- **Also known as:** GHSA-jj27-x85q-crqv

## What is CVE-2023-33177?

CVE-2023-33177 is a high-severity path traversal 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). A path traversal vulnerability exists in the Xibo CMS whereby a specially crafted zip file can be uploaded to the CMS via the layout import function by an authenticated user which would allow creation of files outside of the CMS library directory as the webserver user. This can be used to upload a PHP webshell inside the web root directory and achieve remote code execution as the webserver user. Users should upgrade to version 2.3.17 or 3.3.5, which fix this issue. Customers who host their CMS with Xibo Signage have already received an upgrade or patch to resolve this issue regardless of the CMS version that they are running.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Xibosignage Xibo.

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

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

## Is CVE-2023-33177 being exploited?

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

Public exploit code:

- This exploit demonstrates a **path traversal vulnerability** in Xibo CMS (CVE-2023-33177) that allows remote code execution through malicious layout imports. (github_poc): https://github.com/complexusprada/Xibo-CMS-Zip-Slip-RCE-Exploit-CVE-2023-33177
- xibocms 3.3.4 - RCE (exploitdb)
- Xibo CMS CVE-2023-33177 Vulnerability Tester (github_poc): https://github.com/kaxm23/-CVE-2023-33177-

## Other vulnerabilities in xibosignage xibo-cms

- [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)
- [CVE-2013-4889](https://insights.sbomify.com/CVE-2013-4889/): Cross-site request forgery in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-33177 is a high-severity path traversal 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-33177 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-33177/ (Markdown: https://insights.sbomify.com/CVE-2023-33177/index.md)
```

## Sources

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

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