{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17207 exists.","fix":"No fix has been published for CVE-2018-17207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-17207 is a critical code injection vulnerability in n/a, published on 19 Sep 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-17207 and fix it if it is affected.\n\nWhat it is: CVE-2018-17207 is a critical code injection vulnerability in n/a, published on 19 Sep 2018. 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-2018-17207 exists.\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-17207/ (Markdown: https://insights.sbomify.com/CVE-2018-17207/index.md)","id":"CVE-2018-17207","markdown":"https://insights.sbomify.com/CVE-2018-17207/index.md","name":"CVE-2018-17207","record":{"aliases":["GHSA-4hvf-vmqm-x8p3"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress Duplicator plugin","requires_auth":"none","summary":"Attackers can achieve arbitrary code execution by injecting PHP into configuration files via leftover installer scripts in the Duplicator plugin.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"duplicator","vendor":"awesomemotive"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"An issue was discovered in Snap Creek Duplicator before 1.2.42. By accessing leftover installer files (installer.php and installer-backup.php), an attacker can inject PHP code into wp-config.php during the database setup step, achieving arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2018-08-29","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":1,"refs":[{"date":"2018-08-29","kind":"metasploit","ref":"exploit/multi/php/wp_duplicator_code_inject","stars":null,"title":"Snap Creek Duplicator WordPress plugin code injection"},{"date":"2019-02-01T20:36:08Z","kind":"github_poc","ref":"https://github.com/cved-sources/cve-2018-17207","stars":0,"title":"cve-2018-17207"},{"date":null,"kind":"nuclei","ref":"http/cves/2018/CVE-2018-17207.yaml","stars":null,"title":"WordPress Duplicator Plugin \u003c 1.2.42 - Arbitrary Code Execution"}],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2018-17207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Command injection in n/a","id":"CVE-2018-17208"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-17206"},"products":["n/a"],"published":"2018-09-19","related":[{"cvss_score":7.5,"headline":"WordPress Snap Creek Duplicator Plugin File Download","id":"CVE-2020-11738","kev_date_added":"2021-11-03","published":"2020-04-13"},{"cvss_score":9.8,"headline":"Duplicator \u003c 1.3.0 - Unauthenticated RCE","id":"CVE-2018-25095","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.5,"headline":"Duplicator \u003c 1.5.7.1; Duplicator Pro \u003c 4.5.14.2 - Unauthenticated Sensitive Data Exposure","id":"CVE-2023-6114","kev_date_added":null,"published":"2023-12-26"},{"cvss_score":7.5,"headline":"Duplicator \u003c 1.4.7 - Unauthenticated Backup Download","id":"CVE-2022-2551","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":7.1,"headline":"WordPress Duplicator Pro Plugin \u003c= 4.5.11 is vulnerable to Cross Site Scripting (XSS)","id":"CVE-2023-33309","kev_date_added":null,"published":"2023-05-28"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-7543","kev_date_added":null,"published":"2018-03-26"}],"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)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Attackers can achieve arbitrary code execution by injecting PHP into configuration files via leftover installer scripts in the Duplicator plugin.","url":"https://insights.sbomify.com/CVE-2018-17207/"}