# CVE-2019-25486: Varient 1.6.1 SQL Injection via user_id Parameter

> Unauthenticated attackers can inject SQL via the user_id parameter to bypass authentication and extract sensitive database information.

- **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:** 11 Mar 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-q8hg-mrch-vx5c

## What is CVE-2019-25486?

CVE-2019-25486 is a high-severity SQL injection vulnerability in Varient SQL Inj., published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Varient 1.6.1 contains an SQL injection vulnerability that allows unauthenticated attackers to manipulate database queries by injecting SQL code through the user_id parameter. Attackers can submit POST requests with crafted SQL payloads in the user_id field to bypass authentication and extract sensitive database information.

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

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


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

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

## Is CVE-2019-25486 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25486 is a high-severity SQL injection vulnerability in Varient SQL Inj., published on 11 Mar 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-25486 exists.

Affected product: Varient SQL Inj.. 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-25486/ (Markdown: https://insights.sbomify.com/CVE-2019-25486/index.md)
```

## Sources

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

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