# CVE-2025-4687: Account pre-hijacking through invite misuse

> Attackers can hijack accounts by exploiting invite logic, allowing unauthorized management of victim companies in Teltonika RMS.

- **Severity:** High 7.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:L/VI:L/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 May 2025
- **Updated:** 29 May 2025
- **Also known as:** GHSA-78jm-3rg9-qvxq

## What is CVE-2025-4687?

CVE-2025-4687 is a high-severity vulnerability in Teltonika Networks RMS, published on 29 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

In Teltonika Networks Remote Management System (RMS), it is possible to perform account pre-hijacking by misusing the invite functionality. If a victim has a pending invite and registers to the platform directly, they are added to the attackers company without their knowledge. The victims account and their company can then be managed by the attacker.This issue affects RMS: before 5.7.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2025-4687 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-4687 is a high-severity vulnerability in Teltonika Networks RMS, published on 29 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4687 exists.

Affected product: Teltonika Networks RMS. 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-4687/ (Markdown: https://insights.sbomify.com/CVE-2025-4687/index.md)
```

## Sources

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

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