CVE-2018-17207 in the critical feed json
An issue was discovered in Snap Creek Duplicator before 1.2.42.
published 2018-09-19 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-8969
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 60.1%
- EPSS 60.1% chance of exploitation in 30 days, percentile 99.1%
- public exploits
- 1
- Metasploit, plus a Nuclei check
Summary
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.
Patch / fix
- awesomemotive duplicator 1.2.42
Timeline
- First public exploit (Metasploit exploit/multi/php/wp_duplicator_code_inject)
- Published
Exploit prediction
60.09% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/multi/php/wp_duplicator_code_inject Snap Creek Duplicator WordPress plugin code injection metasploit exploit, manual rank, 2018-08-29
- Nuclei template WordPress Duplicator Plugin < 1.2.42 - Arbitrary Code Execution nuclei detection template
- synacktiv.com https://www.synacktiv.com/ressources/advisories/WordPress_Duplicator-1.2.40-RCE.pdf referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-94 Improper Control of Generation of Code
- Technology feeds
References
-
synacktiv.com
/ressources/advisories/WordPress_Duplicator-1.2.40-RCE.pdf
exploit, third-party-advisory
-
snapcreek.com
/duplicator/docs/changelog/?lite
vendor-advisory
Sources
- CVE List CVE-2018-17207
- NVD CVE-2018-17207
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.