# CVE-2025-27406: Icinga Reporting Stored XSS leads to SSRF

> Attackers can inject arbitrary JavaScript into reporting templates, enabling XSS and SSRF when templates are previewed or printed.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-27406, GHSA-7qvq-54vm-r7hx, UBUNTU-CVE-2025-27406

## What is CVE-2025-27406?

CVE-2025-27406 is a high-severity cross-site scripting vulnerability in icingaweb2-module-reporting, published on 26 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

Upgrade to a fixed version.

## Is CVE-2025-27406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27406 is a high-severity cross-site scripting vulnerability in icingaweb2-module-reporting, published on 26 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-27406 in the wild and no public exploit code.

Affected product: icingaweb2-module-reporting. 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-27406/ (Markdown: https://insights.sbomify.com/CVE-2025-27406/index.md)
```

## Sources

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

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