OptionTree <= 2.7.3 - Authenticated (Editor+) PHP Object Injection
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- OptionTree
- Affected Version
<= 2.7.3- CVSS
- 6.6Medium
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-66620
At a glance
CVE-2026-66620 is a medium-severity Deserialization of Untrusted Data vulnerability in the OptionTree WordPress plugin, affecting versions <= 2.7.3. It carries a CVSS score of 6.6 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Editor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Ananda Dhakal.
Vulnerability Overview
The OptionTree plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 2.7.3. This is due to deserialization of untrusted input. This makes it possible for authenticated attackers, with editor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. 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
Reaching this weakness in OptionTree <= 2.7.3 takes an account at Editor 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. No fixed build of this plugin is recorded for OptionTree yet, so installs running <= 2.7.3 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?
An attacker needs Editor 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. 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
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C