{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85200 exists.","fix":"No fix has been published for CVE-2026-85200 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85200 is a high-severity path traversal vulnerability in ninjew GEO my WP, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85200 and fix it if it is affected.\n\nWhat it is: CVE-2026-85200 is a high-severity path traversal vulnerability in ninjew GEO my WP, published on 12 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-85200 exists.\n\nAffected product: ninjew GEO my WP. 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-2026-85200/ (Markdown: https://insights.sbomify.com/CVE-2026-85200/index.md)","id":"CVE-2026-85200","markdown":"https://insights.sbomify.com/CVE-2026-85200/index.md","name":"CVE-2026-85200","record":{"aliases":["GHSA-6hw9-7gx5-mw88"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can exploit a Local File Inclusion vulnerability in the GEO my WP WordPress plugin to execute arbitrary PHP code or read sensitive data.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-98","name":"Improper Control of Filename for Include/Require Statement in PHP Program"}],"description":"The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_ajax_info_window_loader function. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. In environments where PEAR is installed with register_argc_argv enabled, this file inclusion can be leveraged to write and execute arbitrary PHP code, achieving full remote code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-85200.yaml","stars":null,"title":"GEO my WP \u003c=4.5.5.3 - Unauthenticated Local File Inclusion"}],"tier":"weaponised"},"has_fix":false,"headline":"GEO my WP \u003c= 4.5.5.3 - Unauthenticated Local File Inclusion","id":"CVE-2026-85200","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":10,"next":{"headline":"Denial of service in Eclipse Ankaios","id":"CVE-2026-85201"},"packages":[],"prev":{"headline":"Path traversal in Eclipse aeriOS","id":"CVE-2026-85199"},"products":["GEO my WP"],"published":"2026-09-12","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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["ninjew"]},"summary":"Unauthenticated attackers can exploit a Local File Inclusion vulnerability in the GEO my WP WordPress plugin to execute arbitrary PHP code or read sensitive data.","url":"https://insights.sbomify.com/CVE-2026-85200/"}