# CVE-2021-41372: Power BI Report Server Spoofing Vulnerability

> Attackers can upload malicious templates to execute scripts and escalate privileges via XSS and CSRF in Power BI Report Server.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Nov 2021
- **Updated:** 19 Aug 2026
- **Also known as:** GHSA-3w9m-7j3j-w9p6

## What is CVE-2021-41372?

CVE-2021-41372 is a high-severity cross-site scripting vulnerability in Microsoft Power BI Report Server version 1.11.8091.10468, published on 10 Nov 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Scripting (XSS) and Cross-Site Request Forgery (CSRF) vulnerability exists when Power BI Report Server Template file (pbix) containing HTML files is uploaded to the server and HTML files are accessed directly by the victim.
Combining these 2 vulnerabilities together, an attacker is able to upload malicious Power BI templates files to the server using the victim's session and run scripts in the security context of the user and perform privilege escalation in case the victim has admin privileges when the victim access one of the HTML files present in the malicious Power BI template uploaded.
The security update addresses the vulnerability by helping to ensure that Power BI Report Server properly sanitize file uploads.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2021-41372?

It affects 1 product.


Products: Microsoft Power Bi Report Server.

## How do I fix CVE-2021-41372?

No fix has been published for CVE-2021-41372 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-41372 being exploited?

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

## Other vulnerabilities in Microsoft Power BI Report Server version 1.11.8091.10468

- [CVE-2026-65811](https://insights.sbomify.com/CVE-2026-65811/): Power BI Remote Code Execution Vulnerability (high 8.8)
- [CVE-2023-21806](https://insights.sbomify.com/CVE-2023-21806/): Power BI Report Server Spoofing Vulnerability (high 8.2)
- [CVE-2026-58647](https://insights.sbomify.com/CVE-2026-58647/): Microsoft PowerBI Report Server Spoofing Vulnerability (high 8.0)
- [CVE-2026-21229](https://insights.sbomify.com/CVE-2026-21229/): Power BI Remote Code Execution Vulnerability (high 8.0)
- [CVE-2021-26859](https://insights.sbomify.com/CVE-2021-26859/): Microsoft Power BI Information Disclosure Vulnerability (high 7.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41372 and fix it if it is affected.

What it is: CVE-2021-41372 is a high-severity cross-site scripting vulnerability in Microsoft Power BI Report Server version 1.11.8091.10468, published on 10 Nov 2021. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2021-41372 in the wild and no public exploit code.

Affected product: Microsoft Power BI Report Server version 1.11.8091.10468. 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-2021-41372/ (Markdown: https://insights.sbomify.com/CVE-2021-41372/index.md)
```

## Sources

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

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