CVE-2016-20103: Unauthenticated Path Traversal in Cherry Plugin for WordPress
Cherry Plugin for WordPress before version 1.2.7 contains a path traversal vulnerability in its import/export download handler. The handler passes the attacker-controlled 'file' GET parameter directly to readfile() without sanitization, allowing traversal outside the intended directory and disclosure of arbitrary files readable by the web server.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthenticated attackers can disclose sensitive server-side files, including WordPress configuration data containing database credentials. File access is limited by the web server process's filesystem permissions. Exposed credentials may enable further compromise where the corresponding services are accessible.
Remediation
Patch, then assume compromise.
Upgrade Cherry Plugin for WordPress to version 1.2.7 or later.
Exploits
No public exploits tracked yet. Mallory keeps watching.
References
Frequently asked questions
- Is CVE-2016-20103 exploited in the wild?
- Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2016-20103?
- Yes. As of Nov 19, 2026, Mallory has reports of a public exploit for CVE-2016-20103.
- Is there a patch for CVE-2016-20103?
- Upgrade Cherry Plugin for WordPress to version 1.2.7 or later.
- How severe is CVE-2016-20103?
- CVE-2016-20103 has a CVSS v4 score of 8.7 (High) and an EPSS score of 0.61% (50th percentile) as of Nov 19, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.