dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-10746

MEDIUM · 6.5 CVSS v3.1 Published 2025-10-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/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 Integrate Dynamics 365 CRM plugin for WordPress is vulnerable to unauthorized access in all versions up to, and including, 1.0.9. This is due to missing capability checks and nonce verification on functions hooked to 'init'. This makes it possible for unauthenticated attackers to deactivate the plugin, tamper with OAuth configuration, and trigger test connections that expose sensitive data via direct request to vulnerable endpoints granted they can craft malicious requests with specific parameters.

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 Integrate Dynamics 365 CRM plugin for WordPress lacks capability checks and nonce verification on functions hooked to the 'init' action. This allows unauthenticated attackers to send direct requests with specific parameters to deactivate the plugin, modify OAuth configuration settings, and trigger test connections that expose sensitive data.

MitigationUpdate to version 1.0.10 or later which contains proper capability checks and nonce verification. If no update is available, remove the plugin until patched.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 plugin installation and version
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, locate 'Integrate Dynamics 365 CRM', and record the version number displayed
    Affected if The installed version is lower than 1.0.10 or the version cannot be determined (plugin may be outdated/unlisted)
  2. Check plugin file header version
    If server file access is available, locate the main plugin file (typically integrate-dynamics-365-crm.php in wp-content/plugins) and read the 'Version:' value from the plugin comment header
    Affected if The version in the file header is below 1.0.10
  3. Inspect init hook functions for missing capability checks
    Examine the plugin source code for functions hooked to 'add_action("init", ...)' and verify if they include current_user_can() or similar capability checks before executing sensitive operations
    Affected if Functions hooked to init process requests without verifying user capabilities
  4. Check for missing nonce verification on init actions
    Review the same init hook functions for wp_verify_nonce() or check_admin_referer() calls before processing $_GET or $_POST parameters
    Affected if No nonce verification is performed before processing parameters that modify plugin settings or deactivate the plugin

You are affected if the Integrate Dynamics 365 CRM plugin is installed with a version below 1.0.10 and lacks capability/nonce checks on its init hook functions.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to version 1.0.10 or later which contains proper capability checks and nonce verification. If no update is available, remove the plugin until patched.

Recommended fix Moderate confidence

Update to the latest version of Integrate Dynamics 365 CRM (version 1.0.10 or higher)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the 'Integrate Dynamics 365 CRM' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Verify the update was successful and the plugin is functioning normally

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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