Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Critical

PHP Object Injection in WordPress Appointments Plugin

IdentifiersCVE-2017-20206CWE-502· Deserialization of Untrusted Data

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

Successful exploitation allows an unauthenticated remote attacker to inject PHP objects into the vulnerable application context. Based on the provided content, attackers were observed leveraging this to create backdoors, implying compromise of site integrity and the ability to establish persistent unauthorized access. The associated CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) indicates potential for complete compromise of confidentiality, integrity, and availability on affected systems.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling the Appointments plugin until it can be updated. Treat any site running a vulnerable version as potentially compromised if it was internet-accessible. Review for suspicious files, unexpected theme or plugin modifications, and anomalous administrator activity. Monitor logs and file integrity for evidence of exploitation involving the 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.

Update the Appointments plugin to a version that fixes the insecure deserialization issue; the vulnerable range is up to and including 2.2.1, so affected installations should move to a patched release or the latest available version immediately. Because the content states the vulnerability was actively exploited to create backdoors, remediation should also include incident response actions on potentially exposed sites: inspect the WordPress installation for unauthorized files or code, remove any discovered backdoors or malicious modifications, and review relevant logs for signs of unauthorized access or exploitation activity.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

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.

VendorProductType
WpmudevAppointmentsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.