CVE-2026-1426
Authenticated PHP Object Injection in WP plugin; requires POP chain for RCE.
Is CVE-2026-1426 being exploited?
Not confirmed. CVE-2026-1426 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.46% probability of exploitation in the next 30 days.
How severe is CVE-2026-1426?
CVE-2026-1426 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-1426?
Not known from our data. No patch reference has been recorded for CVE-2026-1426, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-1426 affect?
CVE-2026-1426 affects WordPress, Advanced AJAX Product Filters (WordPress plugin), Live Composer compatibility layer. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-1426?
Disable plugin; patch when available; monitor for POP-based abuse
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Auth user (Author+) can inject a PHP object; no impact unless a POP chain exists in another plugin/theme; with POP chain, may delete files, exfiltrate data, or execute code.
Patch when possible
- affected<= 3.1.9.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.