dbcve.org
Icinga Web 2Application · Icinga

CVE-2025-27609

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 allows an attacker to craft a request that, once transmitted to a victim's Icinga Web, allows to embed arbitrary Javascript into it and to act on behalf of that user. This issue has been resolved in versions 2.11.5 and 2.12.3 of Icinga Web 2. As a workaround, those who have Icinga Web 2.12.2 may enable a content security policy in the application settings. Any modern browser with a working CORS implementation also sufficiently guards against the vulnerability.

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 before versions 2.11.5 and 2.12.3 contains a cross-site scripting (XSS) vulnerability that allows attackers to craft malicious requests embedding arbitrary JavaScript into the application, enabling session hijacking or actions on behalf of authenticated users.

MitigationUpgrade to Icinga Web 2 version 2.11.5 or 2.12.3 or later. Alternatively, enable Content Security Policy in application settings or ensure modern browser CORS protections are active.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Icinga Web 2 version
    Run the command icingaweb2 --version or check the version file in your Icinga Web 2 installation directory, typically found in the about or about/show section of the web interface
    Affected if The version is less than 2.11.5 OR greater than or equal to 2.12.0 but less than 2.12.3
  2. Confirm authentication is in use
    Verify that Icinga Web 2 is configured with user authentication enabled. Check your authentication configuration in etc/icingaweb2/authentication.ini or via the web interface under Configuration > Authentication
    Affected if Authentication is enabled, as the XSS vulnerability targets authenticated user sessions
  3. Check for existing sessions
    Review active user sessions in the web interface or check etc/icingaweb2/sessions.ini to confirm users have active authenticated sessions
    Affected if Authenticated sessions exist, as the XSS could be used to hijack these sessions
  4. Inspect Content Security Policy configuration
    Navigate to Configuration > Application > Security in the Icinga Web 2 web interface or check the security section in etc/icingaweb2/config.ini for Content-Security-Policy settings
    Affected if CSP is disabled or not configured, meaning there is no browser-side protection against the XSS attack

You are affected if your installed Icinga Web 2 version is below 2.11.5 or between 2.12.0 and 2.12.3, and users have active authenticated sessions without CSP protection.

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 to Icinga Web 2 version 2.11.5 or 2.12.3 or later. Alternatively, enable Content Security Policy in application settings or ensure modern browser CORS protections are active.

Recommended fix High confidence

Icinga Web 2 version 2.11.5 or 2.12.3 (depending on your current major version)

  1. If running Icinga Web 2 version 2.11.x: upgrade to version 2.11.5
  2. If running Icinga Web 2 version 2.12.0 through 2.12.2: upgrade to version 2.12.3
  3. After upgrade, verify the vulnerability is resolved by testing that arbitrary JavaScript can no longer be embedded via crafted requests
  4. Alternatively, as a configuration workaround for Icinga Web 2.12.2: navigate to Application Settings and enable Content Security Policy (CSP) headers

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-27609 — 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-27609 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