# CVE-2024-24819: icingaweb2-module-incubator base implementation for HTML forms is susceptible to CSRF

> Attackers can perform unauthorized actions on behalf of users due to missing CSRF token validation in Icinga Web 2 incubator forms.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Feb 2024
- **Updated:** 15 May 2025
- **Also known as:** GHSA-p8vv-9pqq-rm8p

## What is CVE-2024-24819?

CVE-2024-24819 is a medium-severity vulnerability in icingaweb2-module-incubator, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

icingaweb2-module-incubator is a working project of bleeding edge Icinga Web 2 libraries. In affected versions the class `gipfl\Web\Form` is the base for various concrete form implementations [1] and provides protection against cross site request forgery (CSRF) by default. This is done by automatically adding an element with a CSRF token to any form, unless explicitly disabled, but even if enabled, the CSRF token (sent during a client's submission of a form relying on it) is not validated. This enables attackers to perform changes on behalf of a user which, unknowingly, interacts with a prepared link or website. The version 0.22.0 is available to remedy this issue. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2024-24819?

It affects 1 product.


Products: Icinga Icingaweb2-Module-Incubator.

## How do I fix CVE-2024-24819?

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

## Is CVE-2024-24819 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24819 and fix it if it is affected.

What it is: CVE-2024-24819 is a medium-severity vulnerability in icingaweb2-module-incubator, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-24819 in the wild and no public exploit code.

Affected product: icingaweb2-module-incubator. 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-2024-24819/ (Markdown: https://insights.sbomify.com/CVE-2024-24819/index.md)
```

## Sources

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

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