Strategic Overview
- Status
- Unpatched
- Affected Plugin
- A.Williams
- Affected Version
<= 1.3.1- CVSS
- 8.1High
- Weakness type
- CWE-502 · Deserialization of Untrusted Data
- CVE
CVE-2026-65572
At a glance
CVE-2026-65572 is a high-severity Deserialization of Untrusted Data vulnerability in the A.Williams WordPress plugin, affecting versions <= 1.3.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Bonds.
Vulnerability Overview
The A.Williams plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.3.1 via deserialization of untrusted input [from the vulnerable parameter?|in the vulnerable function?]. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, 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 A.Williams <= 1.3.1 takes no account at all. 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 A.Williams yet, so installs running <= 1.3.1 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?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: 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
- Login Security
External References
Related records
Other vulnerabilities in A.Williams
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C