# CVE-2019-25325: Thrive Smart Home 1.1 - 'Smart Home' Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

> Unauthenticated attackers can bypass authentication and access the application via SQL injection in the login endpoint.

- **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:** 12 Feb 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-g6q7-8v7v-98q7

## What is CVE-2019-25325?

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

### Official description

Thrive Smart Home 1.1 contains an SQL injection vulnerability in the checklogin.php endpoint that allows unauthenticated attackers to bypass authentication by manipulating the 'user' POST parameter. Attackers can inject malicious SQL code like ' or 1=1# to manipulate login queries and gain unauthorized access to the application.

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

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


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

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

## Is CVE-2019-25325 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-25325 is a high-severity SQL injection vulnerability in Thrive Smart Home, published on 12 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-25325 exists.

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

## Sources

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

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