# CVE-2018-25192: GPS Tracking System 2.12 SQL Injection via username Parameter

> Unauthenticated attackers can bypass authentication and gain unauthorized access to the GPS Tracking System via SQL injection in the username parameter.

- **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:** 6 Mar 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-w5gc-4qr3-6c8f

## What is CVE-2018-25192?

CVE-2018-25192 is a high-severity SQL injection vulnerability in Sourceforge GPS Tracking System, published on 6 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GPS Tracking System 2.12 contains an SQL injection vulnerability that allows unauthenticated attackers to bypass authentication by injecting SQL code through the username parameter. Attackers can submit crafted POST requests to the login.php endpoint with SQL injection payloads in the username field to gain unauthorized access without valid credentials.

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

## Which versions are affected by CVE-2018-25192?


## How do I fix CVE-2018-25192?

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

## Is CVE-2018-25192 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-25192 and fix it if it is affected.

What it is: CVE-2018-25192 is a high-severity SQL injection vulnerability in Sourceforge GPS Tracking System, published on 6 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-2018-25192 exists.

Affected product: Sourceforge GPS Tracking 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-2018-25192/ (Markdown: https://insights.sbomify.com/CVE-2018-25192/index.md)
```

## Sources

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

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