# CVE-2025-5485: SinoTrack GPS Receiver Weak Authentication

> Attackers can enumerate predictable device identifiers to access the web management interface of SinoTrack GPS receivers, leading to unauthorized control.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/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 Jun 2025
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-vhwx-7fp7-5q6g

## What is CVE-2025-5485?

CVE-2025-5485 is a high-severity authentication bypass vulnerability in SinoTrack IOT PC Platform, published on 12 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User names used to access the web management interface are limited to 
the device identifier, which is a numerical identifier no more than 10 
digits. A malicious actor can enumerate potential targets by 
incrementing or decrementing from known identifiers or through 
enumerating random digit sequences.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2025-5485?


## How do I fix CVE-2025-5485?

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

## Is CVE-2025-5485 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-5485 and fix it if it is affected.

What it is: CVE-2025-5485 is a high-severity authentication bypass vulnerability in SinoTrack IOT PC Platform, published on 12 Jun 2025. 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-2025-5485 in the wild and no public exploit code.

Affected product: SinoTrack IOT PC Platform. 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-2025-5485/ (Markdown: https://insights.sbomify.com/CVE-2025-5485/index.md)
```

## Sources

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

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