# CVE-2018-17207: Code injection in n/a

> Attackers can achieve arbitrary code execution by injecting PHP into configuration files via leftover installer scripts in the Duplicator plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4hvf-vmqm-x8p3

## What is CVE-2018-17207?

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.

### Official 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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2018-17207?

It affects 1 product.


Products: Awesomemotive Duplicator.

## How do I fix CVE-2018-17207?

No fix has been published for CVE-2018-17207 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-17207 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17207 exists.

Public exploit code:

- Snap Creek Duplicator WordPress plugin code injection (metasploit)
- cve-2018-17207 (github_poc): https://github.com/cved-sources/cve-2018-17207
- WordPress Duplicator Plugin < 1.2.42 - Arbitrary Code Execution (nuclei): http/cves/2018/CVE-2018-17207.yaml

## Other vulnerabilities in n/a

- [CVE-2020-11738](https://insights.sbomify.com/CVE-2020-11738/): WordPress Snap Creek Duplicator Plugin File Download (high 7.5, exploited in the wild)
- [CVE-2018-25095](https://insights.sbomify.com/CVE-2018-25095/): Duplicator < 1.3.0 - Unauthenticated RCE (critical 9.8)
- [CVE-2023-6114](https://insights.sbomify.com/CVE-2023-6114/): Duplicator < 1.5.7.1; Duplicator Pro < 4.5.14.2 - Unauthenticated Sensitive Data Exposure (high 7.5)
- [CVE-2022-2551](https://insights.sbomify.com/CVE-2022-2551/): Duplicator < 1.4.7 - Unauthenticated Backup Download (high 7.5)
- [CVE-2023-33309](https://insights.sbomify.com/CVE-2023-33309/): WordPress Duplicator Pro Plugin <= 4.5.11 is vulnerable to Cross Site Scripting (XSS) (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-17207 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-17207 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-17207/ (Markdown: https://insights.sbomify.com/CVE-2018-17207/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-17207
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-17207
- OSV: https://osv.dev/vulnerability/CVE-2018-17207

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-17207/
Summaries are generated and may contain mistakes; the official description above is the record.