# CVE-2026-19425: Win Men Intermational｜Travel Agency Management System - SQL Injection

> Unauthenticated attackers can inject SQL commands to read, modify, and delete database contents in the Travel Agency Management System.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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:** 11 Aug 2026
- **Updated:** 12 Aug 2026
- **Also known as:** GHSA-mh55-5vhx-83cg

## What is CVE-2026-19425?

CVE-2026-19425 is a critical SQL injection vulnerability in Win Men Intermational Travel Agency Management System, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Travel Agency Management System developed by Win Men Intermational has a SQL Injection vulnerability. Unauthenticated remote attackers can inject arbitrary SQL commands to read, modify, and delete database contents.

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

## Which versions are affected by CVE-2026-19425?


## How do I fix CVE-2026-19425?

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

## Is CVE-2026-19425 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19425 and fix it if it is affected.

What it is: CVE-2026-19425 is a critical SQL injection vulnerability in Win Men Intermational Travel Agency Management System, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19425 in the wild and no public exploit code.

Affected product: Win Men Intermational Travel Agency Management System. 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-2026-19425/ (Markdown: https://insights.sbomify.com/CVE-2026-19425/index.md)
```

## Sources

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

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