# CVE-2018-18420: Zenario CMS vulnerable to CSRF

> A Cross-Site Request Forgery vulnerability in Zenario CMS allows attackers to perform unauthorized actions on behalf of authenticated users.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-22cq-xxr9-jrrv

## What is CVE-2018-18420?

CVE-2018-18420 is a high-severity vulnerability in n/a, published on 19 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability was discovered in the 8.3 version of Zenario Content Management System via the admin/organizer.ajax.php?path=zenario__content%2Fpanels%2Fcontent URI.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2018-18420?

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 | None |
| `tribalsystems/zenario` | Packagist | All versions | None |

Products: Tribalsystems Zenario.

## How do I fix CVE-2018-18420?

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

## Is CVE-2018-18420 being exploited?

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

## Other vulnerabilities in n/a

- [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-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)
- [CVE-2022-23043](https://insights.sbomify.com/CVE-2022-23043/): File upload restriction bypass in Zenario CMS (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-18420 and fix it if it is affected.

What it is: CVE-2018-18420 is a high-severity vulnerability in n/a, published on 19 Oct 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-18420 in the wild and no public exploit code.

Affected packages and fixed versions:
- tribalsystems/zenario (Packagist): affected all versions; no fix listed
- tribalsystems/zenario (Packagist): affected all versions; no fix listed

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

## Sources

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

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