Row Seats Core < 2.68 - PHP Object Injection
Strategic Overview
- Status
- Patched in 2.68
- Affected Plugin
- Row Seats Core
- Affected Version
< 2.68- CVSS
- 7.2High
- 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 Row Seats Core WordPress plugin, affecting versions < 2.68. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 2.68; sites on affected versions should update now. Disclosed February 2017.
Vulnerability Overview
The Row Seats Core plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 2.66 via deserialization of untrusted input from several parameters such as 'mycartitems'. This allows 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, with low attack complexity — no special timing or configuration is needed, 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
Row Seats Core < 2.68 carries this weakness at mycartitems, 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 Row Seats Core the fix is 2.68: builds < 2.68 are affected, anything from 2.68 onward is not.
Remediation
Update to version 2.68, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Row Seats Core: 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: Row Seats Core 2.68 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C