# CVE-2018-18246: Cross-site request forgery in n/a

> Attackers can force users to disable monitoring or enable setup modules via CSRF, compromising Icinga Web 2 security.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **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:** Yes
- **Published:** 17 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-18246, GHSA-4hph-9j96-cwr9, UBUNTU-CVE-2018-18246

## What is CVE-2018-18246?

CVE-2018-18246 is a medium-severity vulnerability in n/a, published on 17 Dec 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

Icinga Web 2 before 2.6.2 has CSRF via /icingaweb2/config/moduledisable?name=monitoring to disable the monitoring module, or via /icingaweb2/config/moduleenable?name=setup to enable the setup module.

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

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

It affects 1 product.


Products: Icinga Icinga Web 2.

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

Upgrade to a fixed version.

## Is CVE-2018-18246 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-18249](https://insights.sbomify.com/CVE-2018-18249/): Code injection in n/a (critical 9.8)
- [CVE-2022-24715](https://insights.sbomify.com/CVE-2022-24715/): Arbitrary code execution for authenticated users in Icinga Web 2 (high 8.5)
- [CVE-2025-27404](https://insights.sbomify.com/CVE-2025-27404/): Icinga Web 2 DOM-based XSS vulnerability (high 7.7)
- [CVE-2025-27405](https://insights.sbomify.com/CVE-2025-27405/): Icinga Web 2 has XSS in embedded content (high 7.7)
- [CVE-2022-24716](https://insights.sbomify.com/CVE-2022-24716/): Path traversal in Icinga Web 2 (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18246 is a medium-severity vulnerability in n/a, published on 17 Dec 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-18246 in the wild and no public exploit code.

Affected product: n/a. 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-2018-18246/ (Markdown: https://insights.sbomify.com/CVE-2018-18246/index.md)
```

## Sources

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

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