{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-21031 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-21031 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-21031 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-21031 and fix it if it is affected.\n\nWhat it is: CVE-2018-21031 is a medium-severity authentication bypass vulnerability in n/a, published on 18 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-21031 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-21031/ (Markdown: https://insights.sbomify.com/CVE-2018-21031/index.md)","id":"CVE-2018-21031","markdown":"https://insights.sbomify.com/CVE-2018-21031/index.md","name":"CVE-2018-21031","record":{"aliases":["GHSA-9qh9-xp4m-mxph"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Plex monitoring tool","requires_auth":"low_privilege","summary":"Remote attackers can bypass access controls in Plex Media Server by retrieving the X-Plex-Token from vulnerable Tautulli instances.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"media_server","vendor":"plex"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"Tautulli versions 2.1.38 and below allows remote attackers to bypass intended access control in Plex Media Server because the X-Plex-Token is mishandled and can be retrieved from Tautulli. NOTE: Initially, this id was associated with Plex Media Server 1.18.2.2029-36236cc4c as the affected product and version. Further research indicated that Tautulli is the correct affected product.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2018-21031","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-21032"},"packages":[],"prev":{"headline":"Cross-site scripting in Jupyter Notebook","id":"CVE-2018-21030"},"products":["n/a"],"published":"2019-11-18","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can bypass access controls in Plex Media Server by retrieving the X-Plex-Token from vulnerable Tautulli instances.","url":"https://insights.sbomify.com/CVE-2018-21031/"}