# CVE-2018-25041: uTorrent JSON RPC Server privileges management

> Remote attackers can exploit the JSON RPC Server in uTorrent to escalate privileges, requiring an upgrade to mitigate.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jun 2022
- **Updated:** 15 Apr 2025
- **Also known as:** GHSA-mf7m-rm6j-7h8r

## What is CVE-2018-25041?

CVE-2018-25041 is a medium-severity vulnerability in unspecified uTorrent, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in uTorrent. It has been rated as critical. Affected by this issue is some unknown functionality of the component JSON RPC Server. The manipulation leads to privilege escalation. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Utorrent Web.

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

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

## Is CVE-2018-25041 being exploited?

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

## Other vulnerabilities in unspecified uTorrent

- [CVE-2018-25040](https://insights.sbomify.com/CVE-2018-25040/): uTorrent Web HTTP RPC Server privileges management (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25041 is a medium-severity vulnerability in unspecified uTorrent, published on 17 Jun 2022. An attacker can exploit it over the internet without logging in, 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-2018-25041 exists.

Affected product: unspecified uTorrent. 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-25041/ (Markdown: https://insights.sbomify.com/CVE-2018-25041/index.md)
```

## Sources

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

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