dbcve.org
Information ExposureWeakness · CWE-200

CVE-2025-10750

MEDIUM · 5.3 CVSS v3.1 Published 2025-10-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
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 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

The PowerBI Embed Reports WordPress plugin (versions up to 1.2.0) exposes a 'testUser' endpoint via the mo_epbr_admin_observer() function hooked on 'init' without any authentication or authorization checks. This allows unauthenticated attackers to retrieve Azure AD user PII (displayName, mail, phones, department) and detailed OAuth error data including Client IDs, error codes, trace IDs, and correlation IDs.

MitigationUpgrade to plugin version 1.2.1 or later which adds proper capability checks and authentication verification to the testUser endpoint. Alternatively, implement WordPress nonce verification and capability checks (e.g., manage_options) on the endpoint until the patch can be applied.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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. Verify PowerBI Embed Reports plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PowerBI Embed Reports' or check the plugin header file for the version number in wp-content/plugins/powerbi-embed-reports/powerbi-embed-reports.php
    Affected if Plugin is installed and active
  2. Determine installed plugin version
    Check the plugin version in the plugin header comment or in the WordPress plugins admin page under the plugin name
    Affected if Version is 1.2.0 or earlier (versions up to and including 1.2.0 are affected)
  3. Test unauthenticated access to testUser endpoint
    Send a GET or POST request to your WordPress site with the parameter 'action=testUser' (e.g., https://yoursite.com/?action=testUser) without providing any authentication cookies or credentials
    Affected if The endpoint returns Azure AD user PII (displayName, mail, phones, department) or OAuth error data containing Client IDs, error codes, trace IDs, or correlation IDs without requiring login
  4. Inspect the mo_epbr_admin_observer function
    Examine the plugin source code in wp-content/plugins/powerbi-embed-reports/includes/ or similar directory for the mo_epbr_admin_observer function and verify it is hooked to 'init' without capability checks or nonce verification
    Affected if The function is registered on 'init' hook without checking user capabilities or verifying nonces

You are affected if the PowerBI Embed Reports plugin version is 1.2.0 or earlier AND the testUser endpoint responds to unauthenticated requests with Azure AD PII or OAuth error data.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to plugin version 1.2.1 or later which adds proper capability checks and authentication verification to the testUser endpoint. Alternatively, implement WordPress nonce verification and capability checks (e.g., manage_options) on the endpoint until the patch can be applied.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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