{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-14166 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-14166 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14166 is a medium-severity code injection vulnerability in ludwigyou WPMasterToolKit (WPMTK) – All in one plugin, published on 12 Dec 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-14166 and fix it if it is affected.\n\nWhat it is: CVE-2025-14166 is a medium-severity code injection vulnerability in ludwigyou WPMasterToolKit (WPMTK) – All in one plugin, published on 12 Dec 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-14166 in the wild and no public exploit code.\n\nAffected product: ludwigyou WPMasterToolKit (WPMTK) – All in one plugin. 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-14166/ (Markdown: https://insights.sbomify.com/CVE-2025-14166/index.md)","id":"CVE-2025-14166","markdown":"https://insights.sbomify.com/CVE-2025-14166/index.md","name":"CVE-2025-14166","record":{"aliases":["GHSA-7q5g-8744-p89w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"Authenticated attackers with Contributor access can execute arbitrary PHP code via the Code Snippets feature, leading to remote code execution and site compromise.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The WPMasterToolKit plugin for WordPress is vulnerable to PHP Code Injection in all versions up to, and including, 2.13.0. This is due to the plugin allowing Author-level users to create and execute arbitrary PHP code through the Code Snippets feature without proper capability checks. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP code on the server, leading to remote code execution, privilege escalation, and complete site compromise.","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":"WPMasterToolKit (WPMTK) \u003c= 2.13.0 - Authenticated (Contributor+) Code Injection","id":"CVE-2025-14166","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Remove Post Type Slug \u003c= 1.0.2 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-14167"},"packages":[],"prev":{"headline":"Kirim.Email WooCommerce Integration \u003c= 1.2.9 - Cross-Site Request Forgery to Settings Update","id":"CVE-2025-14165"},"products":["WPMasterToolKit (WPMTK) – All in one plugin"],"published":"2025-12-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)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["ludwigyou"]},"summary":"Authenticated attackers with Contributor access can execute arbitrary PHP code via the Code Snippets feature, leading to remote code execution and site compromise.","url":"https://insights.sbomify.com/CVE-2025-14166/"}