CVE-2025-10750: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in cyberlord92 PowerBI Embed Reports
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.
AI Analysis
Technical Summary
The vulnerability CVE-2025-10750 affects the PowerBI Embed Reports plugin for WordPress developed by cyberlord92, specifically all versions up to and including 1.2.0. The root cause is the absence of proper capability checks and authentication verification on the 'testUser' endpoint, which is accessible through the mo_epbr_admin_observer() function hooked into WordPress's 'init' action. This endpoint can be reached by unauthenticated attackers, allowing them to retrieve sensitive Azure Active Directory (Azure AD) user information. The exposed data includes personally identifiable information (PII) such as displayName, email addresses, phone numbers, department details, and detailed OAuth error information like Azure AD Application/Client IDs, error codes, trace IDs, and correlation IDs. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The CVSS v3.1 base score is 5.3, reflecting a medium severity with network attack vector, no privileges required, no user interaction, and limited confidentiality impact. No known exploits have been reported in the wild, and no patches have been linked yet. The vulnerability's exploitation could facilitate reconnaissance and targeted attacks by leaking sensitive identity and configuration data from Azure AD integrations within WordPress environments using this plugin.
Potential Impact
The primary impact of this vulnerability is the unauthorized disclosure of sensitive user information and OAuth error details. Exposure of PII such as names, emails, phone numbers, and department information can lead to privacy violations and may aid attackers in social engineering, phishing, or identity theft campaigns. Disclosure of OAuth error data including Application/Client IDs and trace identifiers can provide attackers with intelligence about the Azure AD environment and application configurations, potentially facilitating further targeted attacks or privilege escalation attempts. While the vulnerability does not directly affect data integrity or availability, the confidentiality breach can undermine organizational security posture and compliance with data protection regulations such as GDPR. Organizations using the affected plugin in environments with sensitive Azure AD integrations are at risk of information leakage to unauthenticated external actors.
Mitigation Recommendations
To mitigate this vulnerability, organizations should immediately update the PowerBI Embed Reports plugin once a patched version is released by the vendor. Until a patch is available, administrators should consider disabling or restricting access to the 'testUser' endpoint by implementing custom access controls or firewall rules to block unauthenticated requests to this endpoint. Reviewing and hardening WordPress plugin permissions and capability checks is critical to prevent unauthorized access. Additionally, organizations should audit their Azure AD logs for unusual access patterns and monitor for any suspicious activity related to exposed Application/Client IDs or OAuth errors. Employing Web Application Firewalls (WAFs) with rules to detect and block attempts to access the vulnerable endpoint can provide interim protection. Finally, educating users and administrators about the risks of information disclosure and enforcing least privilege principles for WordPress plugin usage will reduce exposure.
Affected Countries
United States, Canada, United Kingdom, Germany, France, Australia, India, Japan, Netherlands, Brazil
CVE-2025-10750: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in cyberlord92 PowerBI Embed Reports
Description
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2025-10750 affects the PowerBI Embed Reports plugin for WordPress developed by cyberlord92, specifically all versions up to and including 1.2.0. The root cause is the absence of proper capability checks and authentication verification on the 'testUser' endpoint, which is accessible through the mo_epbr_admin_observer() function hooked into WordPress's 'init' action. This endpoint can be reached by unauthenticated attackers, allowing them to retrieve sensitive Azure Active Directory (Azure AD) user information. The exposed data includes personally identifiable information (PII) such as displayName, email addresses, phone numbers, department details, and detailed OAuth error information like Azure AD Application/Client IDs, error codes, trace IDs, and correlation IDs. The vulnerability is classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The CVSS v3.1 base score is 5.3, reflecting a medium severity with network attack vector, no privileges required, no user interaction, and limited confidentiality impact. No known exploits have been reported in the wild, and no patches have been linked yet. The vulnerability's exploitation could facilitate reconnaissance and targeted attacks by leaking sensitive identity and configuration data from Azure AD integrations within WordPress environments using this plugin.
Potential Impact
The primary impact of this vulnerability is the unauthorized disclosure of sensitive user information and OAuth error details. Exposure of PII such as names, emails, phone numbers, and department information can lead to privacy violations and may aid attackers in social engineering, phishing, or identity theft campaigns. Disclosure of OAuth error data including Application/Client IDs and trace identifiers can provide attackers with intelligence about the Azure AD environment and application configurations, potentially facilitating further targeted attacks or privilege escalation attempts. While the vulnerability does not directly affect data integrity or availability, the confidentiality breach can undermine organizational security posture and compliance with data protection regulations such as GDPR. Organizations using the affected plugin in environments with sensitive Azure AD integrations are at risk of information leakage to unauthenticated external actors.
Mitigation Recommendations
To mitigate this vulnerability, organizations should immediately update the PowerBI Embed Reports plugin once a patched version is released by the vendor. Until a patch is available, administrators should consider disabling or restricting access to the 'testUser' endpoint by implementing custom access controls or firewall rules to block unauthenticated requests to this endpoint. Reviewing and hardening WordPress plugin permissions and capability checks is critical to prevent unauthorized access. Additionally, organizations should audit their Azure AD logs for unusual access patterns and monitor for any suspicious activity related to exposed Application/Client IDs or OAuth errors. Employing Web Application Firewalls (WAFs) with rules to detect and block attempts to access the vulnerable endpoint can provide interim protection. Finally, educating users and administrators about the risks of information disclosure and enforcing least privilege principles for WordPress plugin usage will reduce exposure.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- Wordfence
- Date Reserved
- 2025-09-19T20:28:14.943Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 68f3445827133b8ceda05e2d
Added to database: 10/18/2025, 7:40:08 AM
Last enriched: 2/27/2026, 6:40:18 PM
Last updated: 3/24/2026, 2:05:49 PM
Views: 149
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.