PowerBI Embed Reports <= 1.2.0 - Unauthenticated Sensitive Information Disclosure
Strategic Overview
- Status
- Patched in 1.2.1
- Affected Plugin
- PowerBI Embed Reports
- Affected Version
<= 1.2.0- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2025-10750
At a glance
CVE-2025-10750 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the PowerBI Embed Reports WordPress plugin, affecting versions <= 1.2.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.1; sites on affected versions should update now. Disclosed October 2025, reported by Jonas Benjamin Friedli.
Vulnerability Overview
The PowerBI Embed Reports plugin for WordPress is vulnerable to Sensitive Information Disclosure in all versions up to, and including, 1.2.0. This is due to missing capability checks and authentication verification on the 'testUser' endpoint accessible via the mo_epbr_admin_observer() function hooked on 'init'. This makes it possible for unauthenticated attackers to access sensitive Azure AD user information including personal identifiable information (PII) such as displayName, mail, phones, department, or detailed OAuth error data including Azure AD Application/Client IDs, error codes, trace IDs, and correlation IDs.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
PowerBI Embed Reports <= 1.2.0 carries this weakness at testUser, and reaching it takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For PowerBI Embed Reports the fix is 1.2.1: builds <= 1.2.0 are affected, anything from 1.2.1 onward is not.
Remediation
Update to version 1.2.1, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: PowerBI Embed Reports 1.2.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in PowerBI Embed Reports
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C