CVE-2025-69414VulnerabilityPublished 2 Jan 2026

CVE-2025-69414: Plex Media Server · Incorrect Authorization

Affects Plex Media ServerSource CVE Database V5

Not known to be exploited · CVSS 8.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

8.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PlexMedia Server	Affected <=1.42.2.10156	Fixed in–

AI-suggested

To mitigate CVE-2025-69414 effectively, European organizations should implement the following specific measures: 1) Immediately restrict network access to the Plex Media Server, limiting it to trusted IP ranges and internal networks to reduce exposure. 2) Enforce strict authentication and authorization policies, including monitoring and auditing the use of transient and permanent tokens for anomalous activity. 3) Disable or restrict the /myplex/account API endpoint if feasible until a vendor patch is available. 4) Implement network segmentation to isolate Plex servers from critical infrastructure and sensitive data repositories. 5) Employ multi-factor authentication (MFA) for Plex accounts to reduce the risk of token misuse. 6) Regularly review and revoke unused or suspicious tokens from the Plex account management interface. 7) Stay informed about vendor updates and apply patches promptly once released. 8) Conduct internal penetration testing and vulnerability assessments focusing on token management and API security. 9) Educate users and administrators about the risks associated with token exposure and encourage secure token handling practices. These targeted actions go beyond generic advice by focusing on token lifecycle management, API access control, and network-level protections tailored to Plex Media Server environments.

Description

Plex Media Server (PMS) through 1.42.2.10156 allows retrieval of a permanent access token via a /myplex/account call with a transient access token.

Impact

For European organizations, the impact of CVE-2025-69414 can be significant, particularly for those relying on Plex Media Server for internal media distribution, digital asset management, or content sharing. Unauthorized retrieval of permanent access tokens can lead to unauthorized access to sensitive media libraries, user account information, and potentially other integrated services within the Plex ecosystem. This breach of confidentiality could result in data leakage, privacy violations, and reputational damage. Although the integrity and availability impacts are limited, the exposure of permanent tokens could facilitate further lateral movement or privilege escalation within an organization's network if attackers leverage these tokens to access additional resources. Organizations in sectors such as media production, education, and corporate environments using Plex for content delivery are at heightened risk. The vulnerability's remote exploitability and lack of user interaction requirement increase the likelihood of automated or targeted attacks. Additionally, the cross-scope nature of the vulnerability means that compromise could extend beyond the Plex server itself, potentially affecting connected systems or services.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/lufinkey/vulnerability-research/blob/main/CVE-2025-34158/README.md (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Jan 2026, 19:30 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats