# CVE-2025-61789: Icinga DB Web hidden/protected custom variables are prone to filter enumeration

> Authorized users can enumerate values of hidden or protected custom variables in Icinga DB Web via filter queries, exposing sensitive configuration data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Oct 2025
- **Updated:** 16 Oct 2025
- **Also known as:** DEBIAN-CVE-2025-61789, GHSA-w57j-28jc-8429, UBUNTU-CVE-2025-61789

## What is CVE-2025-61789?

CVE-2025-61789 is a medium-severity vulnerability in icingadb-web, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Icinga DB Web provides a graphical interface for Icinga monitoring. Before 1.1.4 and 1.2.3, an authorized user with access to Icinga DB Web, can use a custom variable in a filter that is either protected by icingadb/protect/variables or hidden by icingadb/denylist/variables, to guess values assigned to it. Versions 1.1.4 and 1.2.3 respond with an error if such a custom variable is used.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2025-61789?

It affects 1 product.


Products: Icinga Icinga Db Web.

## How do I fix CVE-2025-61789?

Upgrade to a fixed version.

## Is CVE-2025-61789 being exploited?

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

## Other vulnerabilities in icingadb-web

- [CVE-2025-53840](https://insights.sbomify.com/CVE-2025-53840/): Icinga DB Web Exposure of Sensitive Information to an Unauthorized Actor vulnerability (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61789 and fix it if it is affected.

What it is: CVE-2025-61789 is a medium-severity vulnerability in icingadb-web, published on 16 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61789 in the wild and no public exploit code.

Affected product: icingadb-web. 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-2025-61789/ (Markdown: https://insights.sbomify.com/CVE-2025-61789/index.md)
```

## Sources

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

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