dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-58112

HIGH · 8.8 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Microsoft Dynamics 365 Customer Engagement (on-premises) 1612 (9.0.2.3034) allows the generation of customized reports via raw SQL queries in an upload of a .rdl (Report Definition Language) file; this is then processed by the SQL Server Reporting Service. An account with the privilege Add Reporting Services Reports can upload a malicious rdl file. If the malicious rdl file is already loaded and it is executable by the user, the Add Reporting Services Reports privilege is not required. A malicious actor can trigger the generation of the report, causing the execution of arbitrary SQL commands in the underlying database. Depending on the permissions of the account running SQL Server Reporting Services, the attacker may be able to perform additional actions, such as accessing linked servers or executing operating system commands.

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

Microsoft Dynamics 365 Customer Engagement on-premises allows users with 'Add Reporting Services Reports' privilege to upload customized .rdl (Report Definition Language) files containing raw SQL queries. These malicious .rdl files are processed by SQL Server Reporting Services, enabling execution of arbitrary SQL commands in the underlying database. Once a malicious .rdl is loaded, any user can trigger its execution without elevated privileges, potentially leading to OS command execution if the SQL Server service account has sufficient permissions.

MitigationRestrict or disable the 'Add Reporting Services Reports' privilege, implement .rdl file validation/sandboxing before SSRS processing, run the SSRS service account with least privilege, and disable or secure linked servers to limit lateral movement.

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

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

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. Identify Dynamics 365 Customer Engagement on-premises installation
    Review installed programs or application inventory for Microsoft Dynamics 365 Customer Engagement (on-premises). Check server documentation or CRM deployment records.
    Affected if Dynamics 365 Customer Engagement on-premises is deployed in the environment.
  2. Locate SQL Server Reporting Services integration
    Verify if SSRS is configured to work with Dynamics 365. Check SSRS configuration files (rsreportserver.config) and the Dynamics reporting extensions configuration.
    Affected if SSRS is integrated with the Dynamics deployment.
  3. Identify users with Add Reporting Services Reports privilege
    Query Dynamics security roles or Permission tables for users or teams assigned the 'Add Reporting Services Reports' privilege. In SQL, check the Privileges table for the privilege named 'prvAddReportingServicesReports' or similar.
    Affected if Any user or team possesses the Add Reporting Services Reports privilege.
  4. Inspect SSRS report definition directories
    Locate the SSRS report catalog database or file share where .rdl files are stored (typically the ReportServer database or /Reports folder). Enumerate .rdl files and review their XML content for suspicious raw SQL queries (look for <Query> elements with embedded SELECT/EXEC/ xp_ commands).
    Affected if Custom .rdl files exist containing raw SQL queries or suspicious stored procedure calls.
  5. Review SQL Server service account privileges
    Check the SQL Server service account permissions using SELECT service_account, status FROM sys.dm_server_services or by inspecting server roles. Identify if the service account has sysadmin, db_owner, or operating system-level privileges.
    Affected if The SQL Server service account running SSRS has elevated privileges beyond db_datareader/db_datawriter.

If Dynamics 365 on-premises is deployed with SSRS integration and any user possesses the Add Reporting Services Reports privilege, the environment is potentially affected; further inspect .rdl files and SQL service account permissions to confirm active exploitation.

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

Restrict or disable the 'Add Reporting Services Reports' privilege, implement .rdl file validation/sandboxing before SSRS processing, run the SSRS service account with least privilege, and disable or secure linked servers to limit lateral movement.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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