CMS Commander – Manage Multiple Sites Plugin <= 2.21 - PHP Object Injection
Strategic Overview
- Status
- Patched in 2.22
- Affected Plugin
- CMS Commander – Manage Multiple Sites
- Affected Version
< 2.22- CVSS
- 8.5High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE pending
At a glance
This record tracks a high-severity Deserialization of Untrusted Data vulnerability in the CMS Commander WordPress plugin, affecting versions < 2.22. It carries a CVSS score of 8.5 (reachable over the network; high confidentiality, integrity, availability impact). The issue is fixed in version 2.22; sites on affected versions should update now. Disclosed June 2016, reported by Yorick Koster,.
Vulnerability Overview
The CMS Commander – Manage Multiple Sites plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.21 via deserialization of untrusted input in the cmsc_authenticate() function. This allows unauthenticated attackers to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-502: Deserialization of Untrusted Data
CMS Commander < 2.22 carries this weakness at cmsc_authenticate(), and reaching it takes a caller who can reach the endpoint. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.
A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For CMS Commander the fix is 2.22: builds < 2.22 are affected, anything from 2.22 onward is not.
Remediation
Update to version 2.22, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to CMS Commander: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: CMS Commander 2.22 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Other vulnerabilities in CMS Commander – Manage Multiple Sites
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C