dbcve.org
Icinga Web 2Application · Icinga

CVE-2025-27405

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 allows an attacker to craft a URL that, once visited by any user, allows to embed arbitrary Javascript into Icinga Web 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.

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 versions prior to 2.11.5 and 2.12.13 contain a reflected XSS vulnerability where crafted URLs can embed arbitrary JavaScript into the application, allowing attackers to execute actions in the context of any user who visits the malicious URL.

MitigationUpgrade to Icinga Web 2 version 2.11.5 or 2.12.3 or later, or alternatively enable Content Security Policy in the application settings as a workaround.

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. Determine installed Icinga Web 2 version
    Check the version file typically located at /usr/share/icingaweb2/composer.json, or run the command: icingaweb2 --version, or look at the version shown in the web interface under About in the help menu
    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. Verify if Content Security Policy is enabled
    Check the Icinga Web 2 configuration file /etc/icingaweb2/config.ini for the 'csp' setting under the [global] section, or inspect the web interface at Configuration > Application > Security
    Affected if CSP is disabled or not set, leaving the XSS vector unprotected
  3. Confirm the application is accessible via web browser
    Verify that the Icinga Web 2 interface is reachable and functional
    Affected if The application is live and exposed to users who could click malicious URLs

A user is affected if their Icinga Web 2 version is below 2.11.5 or between 2.12.0 and 2.12.3, and Content Security Policy is not enabled as a mitigating control.

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, or alternatively enable Content Security Policy in the application settings as a workaround.

Recommended fix High confidence

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

  1. 1. Determine current Icinga Web 2 version by navigating to About > General in the web interface or running: icinga2 --version
  2. 2. For versions < 2.11.5: Plan upgrade to version 2.11.5
  3. 3. For versions >= 2.12.0 and < 2.12.3: Plan upgrade to version 2.12.3
  4. 4. Review Icinga Web 2 upgrade documentation for your distribution: https://icinga.com/docs/icinga-web-2/latest/doc/02-Installation/
  5. 5. Backup current configuration files (typically in /etc/icingaweb2/)
  6. 6. Upgrade Icinga Web 2 using your package manager (e.g., apt-get update && apt-get install icingaweb2 or yum update icingaweb2)
  7. 7. Clear browser cache and session cookies after upgrade
  8. 8. Verify the upgrade was successful and all functionality works as expected
Caveat Standard upgrade precautions apply - review release notes for your version branch before upgrading; ensure configuration compatibility

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
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27405 — 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-27405 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