SecureMoz Security Audit <= 1.0.5 - PHP Object Injection
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- SecureMoz Security Audit
- Affected Version
<= 1.0.5- CVSS
- 6.6Medium
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2015-6828
At a glance
CVE-2015-6828 is a medium-severity Deserialization of Untrusted Data vulnerability in the SecureMoz Security Audit WordPress plugin, affecting versions <= 1.0.5. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). No fixed release has been reported yet; treat installations running this software as exposed. Disclosed September 2015, reported by Scott Arciszewski.
Vulnerability Overview
The tweet_info function in class/__functions.php in the SecureMoz Security Audit plugin 1.0.5 and earlier for WordPress does not use an HTTPS session for downloading serialized data, which allows man-in-the-middle attackers to conduct PHP object injection attacks and execute arbitrary PHP code by modifying the client-server data stream.
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
Reaching this weakness in SecureMoz Security Audit <= 1.0.5 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. No fixed build of this plugin is recorded for SecureMoz Security Audit yet, so installs running <= 1.0.5 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
The attempt arrives as an ordinary request to SecureMoz Security Audit: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C