{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-26985 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-26985 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-26985 is a high-severity path traversal vulnerability in Majestic Support, published on 25 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-26985 and fix it if it is affected.\n\nWhat it is: CVE-2025-26985 is a high-severity path traversal vulnerability in Majestic Support, published on 25 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-26985 in the wild and no public exploit code.\n\nAffected product: Majestic Support. 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-26985/ (Markdown: https://insights.sbomify.com/CVE-2025-26985/index.md)","id":"CVE-2025-26985","markdown":"https://insights.sbomify.com/CVE-2025-26985/index.md","name":"CVE-2025-26985","record":{"aliases":["GHSA-p883-5vm2-vwf3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["data_read","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can exploit a Local File Inclusion vulnerability in the Majestic Support WordPress plugin to read arbitrary files or execute code.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Patchstack","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-98","name":"Improper Control of Filename for Include/Require Statement in PHP Program"}],"description":"Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Majestic Support Majestic Support majestic-support allows PHP Local File Inclusion.This issue affects Majestic Support: from n/a through \u003c= 1.0.6.","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":"WordPress Majestic Support plugin \u003c= 1.0.6 - Local File Inclusion vulnerability","id":"CVE-2025-26985","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"WordPress Pearl Theme \u003c 3.4.8 - Local File Inclusion vulnerability","id":"CVE-2025-26986"},"packages":[],"prev":{"headline":"Cross-site scripting in SMS Alert Order Notifications","id":"CVE-2025-26984"},"products":["Majestic Support"],"published":"2025-02-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Majestic Support"]},"summary":"An attacker can exploit a Local File Inclusion vulnerability in the Majestic Support WordPress plugin to read arbitrary files or execute code.","url":"https://insights.sbomify.com/CVE-2025-26985/"}