CVE-2018-17207

CVE-2018-17207 is a critical-severity vulnerability in Awesomemotive Duplicator with a CVSS 3.x base score of 9.8. Its EPSS exploit-prediction score of 58% places it in the 99th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-94.

Key facts

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.

Frequently asked questions

What is CVE-2018-17207?
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.
How severe is CVE-2018-17207?
CVE-2018-17207 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2018-17207 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 58% (99th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2018-17207?
CVE-2018-17207 affects Awesomemotive Duplicator. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2018-17207?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2018-17207 published?
CVE-2018-17207 was published on 2018-09-19 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Awesomemotive Duplicator

All CVEs affecting Awesomemotive Duplicator →

Other CWE-94 (Code Injection) vulnerabilities

Browse all CWE-94 (Code Injection) vulnerabilities →