CVE-2018-25040 json
uTorrent Web HTTP RPC Server privileges management
published 4y ago modified 4mo ago also EUVD-2018-13812
- cvss
- 6.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 60%
- public exploits
- 0
- none known
Summary
A vulnerability was found in uTorrent Web. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component HTTP RPC Server. The manipulation leads to privilege escalation. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. It is recommended to upgrade the affected component.
Is CVE-2018-25040 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.93% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- vuldb.com https://vuldb.com/?id.113803 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Affected products
- uTorrent Web
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
References
-
vuldb.com
/?id.113803
exploit, third-party-advisory
-
bugs.chromium.org
/p/project-zero/issues/detail?id=1524
issue-tracking, mailing-list, third-party-advisory
-
scmagazineuk.com
/utorrent-apps-vulnerable-to-remote-code-execution-information-disclosure/article/746248/
not-applicable
Sources
- CVE List CVE-2018-25040
- NVD CVE-2018-25040
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.