# CVE-2019-25438: LabCollector 5.423 SQL Injection via login.php

> Unauthenticated attackers can execute arbitrary SQL commands via login.php to extract sensitive database information from LabCollector.

- **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:** 20 Feb 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-qqfx-94p8-6p39

## What is CVE-2019-25438?

CVE-2019-25438 is a high-severity SQL injection vulnerability in LabCollector, published on 20 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LabCollector 5.423 contains multiple SQL injection vulnerabilities that allow unauthenticated attackers to execute arbitrary SQL commands by injecting malicious code through POST parameters. Attackers can submit crafted SQL payloads in the login parameter of login.php or the user_name parameter of retrieve_password.php to extract sensitive database information without authentication.

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

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

It affects 1 product.


Products: Agilebio Labcollector.

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

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

## Is CVE-2019-25438 being exploited?

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

## Other vulnerabilities in LabCollector

- [CVE-2023-33253](https://insights.sbomify.com/CVE-2023-33253/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25438 is a high-severity SQL injection vulnerability in LabCollector, published on 20 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-25438 exists.

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

## Sources

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

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