WordPress plugin
A.Williams security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High1
- Medium0
- Low0
All A.Williams vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Unauthenticated PHP Object Injection ≤1.3.1No patch available | CVE-2026-65572 |
- High8.1Unauthenticated PHP Object Injection
≤1.3.1No patch available
A.Williams: common questions
Does A.Williams have known vulnerabilities?
Yes. VulnCrest Radar lists 1 known vulnerability in A.Williams: 1 high. At least one is not fixed in the latest version.
How do I check which version of A.Williams I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent A.Williams vulnerability?
CVE-2026-65572, published Aug 6, 2026: A.Williams <= 1.3.1 - Unauthenticated PHP Object Injection. Severity: High (CVSS 8.1).
Is any A.Williams vulnerability listed in CISA KEV?
No. None of the known A.Williams vulnerabilities is currently listed in the CISA KEV catalog.