{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69416 exists.","fix":"No fix has been published for CVE-2025-69416 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-69416 is a medium-severity vulnerability in plex.tv backend, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-69416 and fix it if it is affected.\n\nWhat it is: CVE-2025-69416 is a medium-severity vulnerability in plex.tv backend, published on 2 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69416 exists.\n\nAffected product: plex.tv backend. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-69416/ (Markdown: https://insights.sbomify.com/CVE-2025-69416/index.md)","id":"CVE-2025-69416","markdown":"https://insights.sbomify.com/CVE-2025-69416/index.md","name":"CVE-2025-69416","record":{"aliases":["GHSA-ph9c-hmx7-whr8"],"analysis":{"component_type":"cloud_service","fix_type":"no_fix_stated","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Plex Media Server backend","requires_auth":"low_privilege","summary":"Attackers can retrieve unrelated access tokens via the Plex backend, potentially leading to account takeover and unauthorized data access.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"media_server","vendor":"plex"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In the plex.tv backend for Plex Media Server (PMS) through 2025-12-31, a non-server device token can retrieve other tokens (intended for unrelated access) via clients.plex.tv/devices.xml.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Information disclosure in plex.tv backend","id":"CVE-2025-69416","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in plex.tv backend","id":"CVE-2025-69417"},"packages":[],"prev":{"headline":"Missing authorization in Media Server","id":"CVE-2025-69415"},"products":["plex.tv backend"],"published":"2026-01-02","related":[{"cvss_score":8.6,"headline":"Plex Media Server External Control of File Name or Path","id":"CVE-2026-96656","kev_date_added":"2026-10-20","published":"2026-09-23"},{"cvss_score":7.2,"headline":"Plex Media Server Remote Code Execution","id":"CVE-2020-5741","kev_date_added":"2023-03-10","published":"2020-05-08"},{"cvss_score":6.9,"headline":"Plex Media Server Improper Neutralization of Encoded URI Schemes in a Web Page","id":"CVE-2026-96654","kev_date_added":"2026-10-20","published":"2026-09-23"},{"cvss_score":5.3,"headline":"Plex Media Server Server-Side Request Forgery (SSRF)","id":"CVE-2026-96652","kev_date_added":"2026-10-20","published":"2026-09-23"},{"cvss_score":5.3,"headline":"Plex Media Server Server-Side Request Forgery (SSRF)","id":"CVE-2026-96655","kev_date_added":"2026-10-20","published":"2026-09-23"},{"cvss_score":9.8,"headline":"XML external entity in n/a","id":"CVE-2018-13415","kev_date_added":null,"published":"2018-08-13"},{"cvss_score":8.8,"headline":"Cross-site request forgery in Plex Media Server","id":"CVE-2020-5742","kev_date_added":null,"published":"2020-06-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-02","vendors":["Plex"]},"summary":"Attackers can retrieve unrelated access tokens via the Plex backend, potentially leading to account takeover and unauthorized data access.","url":"https://insights.sbomify.com/CVE-2025-69416/"}