# CVE-2022-23043: File upload restriction bypass in Zenario CMS

> Authenticated admins can bypass file upload restrictions to upload malicious .phar files, enabling remote code execution on the server.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6r86-2jm9-9mh4

## What is CVE-2022-23043?

CVE-2022-23043 is a high-severity vulnerability in Zenario CMS, published on 22 Feb 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Zenario CMS 9.2 allows an authenticated admin user to bypass the file upload restriction by creating a new 'File/MIME Types' using the '.phar' extension. Then an attacker can upload a malicious file, intercept the request and change the extension to '.phar' in order to run commands on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2022-23043?

2 open source packages ship an affected version, including tribalsystems/zenario. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tribalsystems/zenario` | Packagist | All versions | 9.2.55826 |
| `tribalsystems/zenario` | Packagist | All versions | 9.2.55826 |

Products: Tribalsystems Zenario.

## How do I fix CVE-2022-23043?

Upgrade tribalsystems/zenario to 9.2.55826 or later.

## Is CVE-2022-23043 being exploited?

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

## Other vulnerabilities in Zenario CMS

- [CVE-2022-44136](https://insights.sbomify.com/CVE-2022-44136/): Zenario CMS is vulnerable to Remote Code Execution (RCE). (critical 9.8)
- [CVE-2021-26830](https://insights.sbomify.com/CVE-2021-26830/): SQL Injection in tribalsystems/zenario (critical 9.1)
- [CVE-2018-18420](https://insights.sbomify.com/CVE-2018-18420/): Zenario CMS vulnerable to CSRF (high 8.8)
- [CVE-2018-5960](https://insights.sbomify.com/CVE-2018-5960/): SQL Injection in Zenario 7.1-7.6 (high 8.8)
- [CVE-2021-42171](https://insights.sbomify.com/CVE-2021-42171/): Unrestricted Upload of File with Dangerous Type in Zenario CMS (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-23043 and fix it if it is affected.

What it is: CVE-2022-23043 is a high-severity vulnerability in Zenario CMS, published on 22 Feb 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23043 in the wild and no public exploit code.

Affected packages and fixed versions:
- tribalsystems/zenario (Packagist): affected all versions; fixed in 9.2.55826
- tribalsystems/zenario (Packagist): affected all versions; fixed in 9.2.55826

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-2022-23043/ (Markdown: https://insights.sbomify.com/CVE-2022-23043/index.md)
```

## Sources

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

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