dbcve.org
Icinga Web 2Application · Icinga

CVE-2025-30164

MEDIUM · 6.1 CVSS v3.1 Published 2025-03-26
Fix available
A fix is available. Upgrade to 2.11.5 / 2.12.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Icinga Web 2 is an open source monitoring web interface, framework and command-line interface. A vulnerability in versions prior to 2.11.5 and 2.12.13 vulnerability allows an attacker to craft a URL that, once visited by an authenticated user (or one that is able to authenticate), allows to manipulate the backend to redirect the user to any location. This issue has been resolved in versions 2.11.5 and 2.12.3 of Icinga Web 2. No known workarounds are available.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Icinga Web 2 contains an open redirect vulnerability where an attacker can craft a malicious URL that, when visited by an authenticated user (or one able to authenticate), manipulates the backend to redirect the user to an arbitrary external location. This could facilitate phishing attacks or session hijacking by tricking users into visiting malicious sites.

MitigationUpgrade Icinga Web 2 to version 2.11.5 or 2.12.3 or later. No workarounds are available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Icinga Web 2Application
Affected:< 2.11.5>= 2.12.0, < 2.12.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Icinga Web 2 installation version
    Run 'icinga2 --version' or check the package manager (dpkg -l icingaweb2 or rpm -qi icingaweb2). Alternatively, check the version file in the installation directory if accessible.
    Affected if The installed version is less than 2.11.5, OR greater than or equal to 2.12.0 but less than 2.12.3
  2. Confirm web interface is accessible
    Verify that the Icinga Web 2 interface is reachable over HTTP/HTTPS. Check if port 80/443 or the configured web server port is listening and accessible.
    Affected if The web interface is exposed to users or network attackers who could trigger the redirect
  3. Identify authentication mechanism
    Review the authentication configuration in /etc/icingaweb2/ roles.ini, auth.ini, or the database-backed authentication setup to confirm which authentication backends are in use.
    Affected if The application uses any authentication method (LDAP, database, or other) that allows user login
  4. Verify redirect functionality exists
    Examine the application logs or web server access logs for any redirect parameters (such as 'redirect=' or 'url=') being used in requests to Icinga Web 2 endpoints.
    Affected if The application processes user-controlled redirect parameters without validation

A user is affected if they run an exposed Icinga Web 2 instance version 2.11.4 or earlier, or version 2.12.0-2.12.2, where authenticated users could be redirected to external sites via manipulated URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.11.5 / 2.12.3 or later
Fixed in 2.11.52.12.3
Interim mitigation

Upgrade Icinga Web 2 to version 2.11.5 or 2.12.3 or later. No workarounds are available.

Recommended fix High confidence

Upgrade to Icinga Web 2 version 2.11.5 (for 2.11.x users) or version 2.12.3 (for 2.12.x users)

  1. 1. Identify the current installed version of Icinga Web 2 by checking your package manager or the version file in the installation directory.
  2. 2. For Icinga Web 2 versions < 2.11.5: Upgrade to version 2.11.5 or later.
  3. 3. For Icinga Web 2 versions >= 2.12.0 and < 2.12.3: Upgrade to version 2.12.3 or later.
  4. 4. Use your package manager to install the update (e.g., apt-get update && apt-get install icingaweb2 for Debian/Ubuntu, or yum/dnf for RHEL-based systems).
  5. 5. After upgrade, clear any cached sessions and verify the installation was successful.
  6. 6. Test that the application functions normally and the open redirect vulnerability is no longer present.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Icinga Web 2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-30164 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-30164 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data