Plex Media Server up to 1.42.2.10156 Device Token /myplex/account operation after expiration
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Plex Media Server up to 1.42.2.10156 and classified as problematic. The impacted element is an unknown function of the file /myplex/account of the component Device Token Handler. Such manipulation leads to operation after expiration. This vulnerability is traded as CVE-2025-69415. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in Plex Media Server up to 1.42.2.10156. It has been rated as problematic. Affected by this issue is an unknown code of the file /myplex/account of the component Device Token Handler. The manipulation with an unknown input leads to a operation after expiration vulnerability. Using CWE to declare the problem leads to CWE-672. The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. Impacted is confidentiality, integrity, and availability. CVE summarizes:
In Plex Media Server (PMS) through 1.42.2.10156, ability to access /myplex/account with a device token is not properly aligned with whether the device is currently associated with an account.
The advisory is available at github.com. This vulnerability is handled as CVE-2025-69415 since 01/02/2026. The exploitation is known to be difficult. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 02/27/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CNA Base Score: 7.1
CNA Vector (MITRE): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Operation after expirationCWE: CWE-672
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/02/2026 Advisory disclosed01/02/2026 CVE reserved
01/02/2026 VulDB entry created
02/27/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2025-69415 (🔒)
GCVE (CVE): GCVE-0-2025-69415
GCVE (VulDB): GCVE-100-339434
Entry
Created: 01/02/2026 21:21Updated: 02/27/2026 16:49
Changes: 01/02/2026 21:21 (62), 02/27/2026 16:49 (11)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.