dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-27406

HIGH · 7.6 CVSS v3.1 Published 2025-03-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Reporting is the central component for reporting related functionality in the monitoring web frontend and framework Icinga Web 2. A vulnerability present in versions 0.10.0 through 1.0.2 allows to set up a template that allows to embed arbitrary Javascript. This enables the attacker to act on behalf of the user, if the template is being previewed; and act on behalf of the headless browser, if a report using the template is printed to PDF. This issue has been resolved in version 1.0.3 of Icinga Reporting. As a workaround, review all templates and remove suspicious 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

Stored XSS vulnerability in Icinga Reporting allows attackers to embed arbitrary JavaScript into templates. When users preview these templates or generate PDF reports using them, the malicious script executes in their browser context, enabling session hijacking and actions performed on behalf of authenticated users.

MitigationUpgrade to Icinga Reporting version 1.0.3 or later. As an immediate workaround, audit all reporting templates and remove any suspicious JavaScript or unexpected settings.

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

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

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

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 Reporting version
    Run the icinga2 command line tool or check the package manager for the icinga-reporting package version. Common commands: 'dpkg -l icinga-reporting' or 'rpm -q icinga-reporting' or check /usr/share/icinga-reporting/config.ini if it exists.
    Affected if The installed version is earlier than 1.0.3 (the fixed release)
  2. Verify reporting module is enabled
    Check if the reporting module is loaded and active in Icinga Web 2. Navigate to the Modules section in Icinga Web 2 configuration, or inspect the modules-enabled directory in the Icinga configuration path.
    Affected if The reporting module is enabled and users can access template preview or PDF generation features
  3. Locate reporting templates directory
    Find the templates storage path. Common locations include /var/lib/icinga-reporting/templates or within the Icinga modules directory. Check the reporting module configuration for the templates.path setting.
    Affected if Templates directory exists and is writable
  4. Inspect templates for suspicious script tags
    Search template files (typically .html, .twig, or template definition files) for occurrences of <script> tags, javascript: URLs, or event handler attributes (onload, onerror, onclick). Use: grep -r '<script' /path/to/templates and grep -r 'javascript:' /path/to/templates.
    Affected if Any template contains embedded JavaScript, Base64-encoded scripts, or event handler attributes that were not intentionally added by an administrator
  5. Review recent template modifications
    Check file modification timestamps on template files to identify recently created or modified templates. Use 'ls -lat' on the templates directory to list files by modification time.
    Affected if Templates were modified recently by an unauthorized account or contain unexpected content

You are affected if Icinga Reporting version is earlier than 1.0.3 AND the reporting module is enabled AND templates can contain user-supplied content that gets rendered in previews or PDF output.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Icinga Reporting version 1.0.3 or later. As an immediate workaround, audit all reporting templates and remove any suspicious JavaScript or unexpected settings.

Recommended fix High confidence

Icinga Reporting version 1.0.3

  1. 1. Back up your current Icinga Reporting installation and database before proceeding with the upgrade.
  2. 2. Update Icinga Reporting to version 1.0.3 using your package manager or by downloading the new version from the Icinga repository.
  3. 3. If using a package manager (e.g., apt, yum, zypper), run: sudo apt-get update && sudo apt-get install icinga-reporting or the equivalent for your distribution.
  4. 4. Alternatively, download version 1.0.3 from the official Icinga GitHub releases page and replace the existing module files.
  5. 5. Clear any cached data by removing the cache directory (typically /var/cache/icingaweb2 or similar).
  6. 6. Verify the installation by logging into Icinga Web 2 and confirming the Reporting module shows version 1.0.3.
  7. 7. As a precaution, review all existing report templates and remove any with suspicious JavaScript or settings as mentioned in the workaround.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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