# CVE-2025-7919: Simopro Technology｜WinMatrix3 Web package - SQL Injection

> Unauthenticated remote attackers can inject SQL commands to read, modify, and delete database contents in WinMatrix3 Web package.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **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:** 21 Jul 2025
- **Updated:** 21 Jul 2025
- **Also known as:** GHSA-25x7-27vj-3vw7

## What is CVE-2025-7919?

CVE-2025-7919 is a high-severity SQL injection vulnerability in Simopro Technology WinMatrix3 Web package, published on 21 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

WinMatrix3 Web package developed by Simopro Technology has a SQL Injection vulnerability, allowing unauthenticated remote attackers to inject arbitrary SQL commands to read, modify, and delete database contents.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-7919 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7919 is a high-severity SQL injection vulnerability in Simopro Technology WinMatrix3 Web package, published on 21 Jul 2025. 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-7919 in the wild and no public exploit code.

Affected product: Simopro Technology WinMatrix3 Web package. 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-7919/ (Markdown: https://insights.sbomify.com/CVE-2025-7919/index.md)
```

## Sources

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

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