# CVE-2025-58112: SQL injection in n/a

> Attackers can execute arbitrary SQL commands via malicious RDL files in Dynamics 365, potentially leading to OS command execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-6gc4-74vr-7h94

## What is CVE-2025-58112?

CVE-2025-58112 is a high-severity SQL injection vulnerability in n/a, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2025-58112?


## How do I fix CVE-2025-58112?

No fix has been published for CVE-2025-58112 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-58112 being exploited?

There is no known exploitation of CVE-2025-58112 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-58112 and fix it if it is affected.

What it is: CVE-2025-58112 is a high-severity SQL injection vulnerability in n/a, published on 18 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-58112 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-58112/ (Markdown: https://insights.sbomify.com/CVE-2025-58112/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-58112
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-58112
- OSV: https://osv.dev/vulnerability/CVE-2025-58112

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-58112/
Summaries are generated and may contain mistakes; the official description above is the record.