CVE-2026-96651 in Media Server
Summary
by MITRE • 09/23/2026
Plex Media Server before 1.43.3.10861 builds a file path from the url parameter without checking it for ../ sequences, allowing path traversal via '/system/agents/media/get'. A remote attacker with a valid session token could read any file that the target user can access. This access includes the PlexOnlineToken, which grants control of the Plex account and server. A LAN-adjacent attacker with a client-supplied X-Forwarded-For header could exploit the same issue.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 09/23/2026
The vulnerability identified in versions of Plex Media Server prior to build 1.43.3.10861 constitutes a critical path traversal flaw within the application's file handling logic. Specifically, the endpoint /system/agents/media/get accepts user-supplied input via the url parameter and constructs a local file system path directly from this value without performing adequate sanitization or validation checks for directory traversal sequences such as ../. This lack of normalization allows an attacker to manipulate the intended file location by injecting relative path components that escape the designated media directories, thereby accessing arbitrary files on the underlying operating system. The root cause lies in insufficient input validation where the application fails to resolve and restrict the final absolute path to a safe base directory before attempting to read or serve the requested resource.
The operational impact of this vulnerability is severe due to its potential for unauthorized data exfiltration and complete account compromise. A remote attacker possessing a valid session token can exploit this flaw to read any file accessible by the Plex Media Server process user. This includes sensitive configuration files, database contents, and most critically, the PlexOnlineToken stored on disk or in memory-accessible locations. The theft of this specific token grants the attacker full control over the victim's Plex account and associated media servers, effectively bypassing authentication mechanisms for subsequent interactions with the service. Beyond immediate credential theft, an attacker could potentially access other private user data such as personal photos, documents, or logs depending on server configuration and file permissions.
The attack surface extends beyond purely remote exploitation scenarios to include LAN-adjacent threats through header manipulation. An adversary positioned within the local network can exploit a related manifestation of this vulnerability by supplying a crafted X-Forwarded-For header. While typically used for logging client IP addresses, in some configurations or specific code paths involving proxy handling, such headers may influence path resolution logic if not properly isolated from file system operations. This vector allows attackers who do not have direct internet-facing access but are on the same local network segment to execute the traversal attack, broadening the scope of potential victims and complicating detection efforts since standard web server logs might appear benign while malicious intent is embedded in HTTP headers rather than URL parameters alone.
From a classification perspective, this vulnerability aligns with CWE-22: Improper Limitation of a Pathname to a Restricted Directory, which describes flaws where software does not properly neutralize special elements within file paths that can cause the path to resolve outside of restricted directories. Additionally, the exploitation technique maps to MITRE ATT&CK tactic TA0001 Initial Access and specifically T1534: Internal Spearphishing or more accurately in this context T1078: Valid Accounts combined with techniques for data exfiltration such as T1005: Data from Local System. The ability to read arbitrary files also touches upon CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, highlighting the risk of leaking credentials and private user data.
Mitigation strategies must prioritize immediate software updates to version 1.43.3.10861 or later where this path traversal issue has been remediated through proper input sanitization and strict directory confinement checks. For environments where patching is not immediately feasible, network segmentation should be enforced to restrict access to the Plex Media Server ports from untrusted LAN segments. Web Application Firewalls may offer limited protection by detecting common ../ sequences in URL parameters or suspicious X-Forwarded-For headers, though such controls are often bypassable with encoding techniques and should not be relied upon as a primary defense. Administrators must also audit server file permissions to ensure the Plex process runs under a restricted user account with minimal privileges, limiting the scope of files that can be read even if an exploitation occurs. Regular monitoring for anomalous access patterns involving sensitive configuration paths or token retrieval operations is recommended to detect potential compromise attempts early.