Cyber Resilience

CVE-2025-29826

Microsoft Dataverse ≤ 3.4.0.1406

Published
13 May 2025
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 7.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
EPSS Score 0.0078 53th percentile
Risk Priority 56 floored blend · peak EPSS

Summary

CVE-2025-29826 is a high-severity Improper Handling of Insufficient Permissions or Privileges (CWE-280) vulnerability in Microsoft Dataverse. Its CVSS base score is 7.3 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-24 (Fail in Known State) and SI-17 (Fail-safe Procedures) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper handling of insufficient permissions or privileges in Microsoft Dataverse allows an authorized attacker to elevate privileges over a network.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1489 Service Stop Impact
Adversaries may stop or disable services on a system to render those services unavailable to legitimate users.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-38139Same product: Microsoft Dataverse
CVE-2026-40371Same vendor: Microsoft
CVE-2024-20699Same vendor: Microsoft
CVE-2026-23666Same vendor: Microsoft
CVE-2023-3280Same vendor: Microsoft
CVE-2026-27910Same vendor: Microsoft
CVE-2024-43559Same vendor: Microsoft
CVE-2023-38171Same vendor: Microsoft
CVE-2023-24938Same vendor: Microsoft
CVE-2023-32008Same vendor: Microsoft

Affected Assets

microsoft
dataverse
≤ 3.4.0.1406

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 7 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.2
  • V8.3.3

Mitigating Controls (NIST 800-53 r5) AI

Requires the system to fail to a known safe state on specified failures, limiting the impact of unhandled exceptional conditions.

Mandates explicit fail-safe procedures triggered by indicated failures, structurally preventing unhandled or mishandled exceptional conditions.

Ensuring access decisions are applied to every request structurally prevents the product from taking unexpected paths when privileges are lacking.

A reference monitor that is always invoked guarantees privilege checks occur, eliminating the root condition for improper insufficient-privilege handling.

Access enforcement directly stops code from proceeding on insufficient privileges by applying authorization checks before resource access.

Requires generation of appropriate error messages on exceptional conditions, directly enforcing correct handling rather than silent or incorrect behavior.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Defining, enforcing and reviewing access permissions with least privilege directly prevents code paths that mishandle insufficient privileges.

PR.PS-06 mostly match
prevents

Secure SDLC practices explicitly require proper exception and error handling during design and coding.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data surfaces adverse events triggered by unhandled permission failures.

PR.PS-04 partial match
prevents

Generating logs of permission-related events enables detection and analysis of improper handling.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect missing or incorrect privilege handling.

prevents

Defines access-control policy that should prevent insufficient-privilege situations.

degrades

Specifies how access rights are granted, reviewed and revoked, directly addressing privilege handling.

degrades

Documented operating procedures may specify exception handling but do not guarantee implementation.

A.8.15 Logging partial match
finds

Logging captures unhandled exceptions, aiding detection but not preventing the weakness.

finds

Monitoring can surface unhandled exceptions but does not enforce proper handling.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248548 OL 8 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-280
  • V-248596 OL 8 must enable the SELinux targeted policy. prevents CWE-280
Oracle Linux 9 (1 rule)
  • V-271452 OL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-280
RHEL 9 (2 rules)
  • V-258078 RHEL 9 must use a Linux Security Module configured to enforce limits on system services. prevents CWE-280
  • V-272496 RHEL 9 must elevate the SELinux context when an administrator calls the sudo command. prevents CWE-280

References