# CVE-2019-25359: SD.NET RIM 4.7.3c - 'idtyp' SQL Injection

> Attackers can inject SQL via POST parameters to manipulate the database and disclose information in SD.NET RIM.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2026
- **Updated:** 19 Feb 2026
- **Also known as:** GHSA-7587-f298-fc3g

## What is CVE-2019-25359?

CVE-2019-25359 is a high-severity SQL injection vulnerability in Sitzungsdienst SD.NET RIM, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SD.NET RIM versions before 4.7.3c contain a SQL injection vulnerability that allows attackers to inject malicious SQL statements through POST parameters 'idtyp' and 'idgremium'. Attackers can exploit this vulnerability by crafting specially formed POST requests to the /vorlagen/ endpoint, enabling unauthorized database manipulation and potential information disclosure.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2019-25359?


## How do I fix CVE-2019-25359?

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

## Is CVE-2019-25359 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25359 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25359 and fix it if it is affected.

What it is: CVE-2019-25359 is a high-severity SQL injection vulnerability in Sitzungsdienst SD.NET RIM, published on 18 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25359 exists.

Affected product: Sitzungsdienst SD.NET RIM. 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-2019-25359/ (Markdown: https://insights.sbomify.com/CVE-2019-25359/index.md)
```

## Sources

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

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