Security readout for executives and security teams
Plain-English summary
This flaw affects Snap Creek Duplicator before 1.2.42 when installer files are left on a WordPress site. If reachable, an attacker could abuse the installer workflow to place PHP code in wp-config.php, leading to code execution on the site.
Executive priority
Treat this as urgent where old Duplicator installer files may remain online. The business risk is full website compromise, especially on public WordPress properties.
Technical view
CVE-2018-17207 involves leftover Duplicator installer.php and installer-backup.php files. During the database setup step, an attacker can inject PHP into wp-config.php and achieve arbitrary code execution. The provided sources identify versions before 1.2.42 but do not provide CVSS or complete affected CPE data.
Likely exposure
Exposure is most likely on WordPress sites that used Duplicator before 1.2.42 and retained web-accessible installer files after migration, backup, or restore work.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The sources describe code execution if leftover installer files are accessible, but the bundle does not prove active exploitation.
Researcher notes
The strongest exposure signal is reachable leftover installer files, not merely plugin presence. Evidence in the bundle is limited on authentication requirements, CVSS, and active exploitation, so validation should focus on file exposure and wp-config.php integrity.
Mitigation direction
- Upgrade Duplicator according to Snap Creek guidance, at least beyond 1.2.42.
- Remove leftover installer.php and installer-backup.php from web roots.
- Block public access to migration or installer artifacts.
- Review wp-config.php for unauthorized PHP changes.
- Restore affected files from known-good backups if tampering is found.
Validation and detection
- Inventory WordPress sites using Snap Creek Duplicator before 1.2.42.
- Check web roots for installer.php and installer-backup.php.
- Confirm installer files are not publicly reachable.
- Review wp-config.php integrity, ownership, and modification time.
- Check web logs for requests to Duplicator installer files.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupDatabase behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-17207 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://snapcreek.com/duplicator/docs/changelog/?liteCVE reference · x_refsource_MISC
- https://www.synacktiv.com/ressources/advisories/WordPress_Duplicator-1.2.40-RCE.pdfCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
