Admin Columns <= 7.0.18 - Authenticated (Contributor+) PHP Object Injection to Remote Code Execution via Custom Field Meta Value
Strategic Overview
- Status
- Patched in 7.0.19
- Affected Plugin
- Admin Columns
- Affected Version
<= 7.0.18- CVSS
- 8.8High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-7654
At a glance
CVE-2026-7654 is a high-severity Deserialization of Untrusted Data vulnerability in the Admin Columns WordPress plugin, affecting versions <= 7.0.18. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 7.0.19; sites on affected versions should update now. Disclosed June 2026, reported by Osvaldo Noe Gonzalez Del Rio (Os).
Vulnerability Overview
The Admin Columns plugin for WordPress is vulnerable to PHP Object Injection leading to Remote Code Execution in versions up to and including 7.0.18. This is due to the use of `unserialize()` without an `allowed_classes` restriction in the `IdsToCollection::get_ids_from_string()` function, which processes attacker-controlled post meta values without proper validation. This makes it possible for authenticated attackers with Contributor-level access and above to inject a serialized PHP object into a post's custom meta field and trigger arbitrary code execution by exploiting a bundled POP gadget chain, resulting in remote code execution as the web server user.
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
Admin Columns <= 7.0.18 carries this weakness at unserialize(), and reaching it takes an account at Contributor level or above. 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 Admin Columns the fix is 7.0.19: builds <= 7.0.18 are affected, anything from 7.0.19 onward is not.
Remediation
Update to version 7.0.19, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: 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: Admin Columns 7.0.19 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C