PHP Object Injection in WordPress Appointments Plugin
CVE-2017-20206 is a critical PHP Object Injection vulnerability in the WordPress Appointments plugin affecting versions up to and including 2.2.1. The flaw is caused by deserialization of untrusted data from the wpmudev_appointments cookie. Because the cookie value is attacker-controlled and processed insecurely, an unauthenticated remote attacker can supply serialized PHP data and trigger object injection. The provided content further states that this vulnerability was actively exploited in the wild using the WP_Theme() class to create backdoors on affected WordPress sites.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
wpmudev_appointments cookie or subsequent persistence mechanisms. These are temporary risk-reduction measures and do not replace applying the vendor fix.Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.