Security readout for executives and security teams
Plain-English summary
This affects WordPress sites using Advanced AJAX Product Filters up to 3.1.9.6, but only under specific conditions. An attacker needs an Author-level or higher account, Live Composer must be active, and real impact depends on another plugin or theme providing a usable PHP object chain.
Executive priority
Prioritize WordPress sites with e-commerce exposure, many content authors, or broad plugin/theme stacks. The vulnerability is high severity, but practical risk depends on authentication, Live Composer usage, and the presence of another vulnerable component.
Technical view
CVE-2026-1426 is a CWE-502 PHP object injection issue in the plugin’s Live Composer compatibility layer. The vulnerable path deserializes untrusted input in shortcode_check. The CVSS score is 8.8, but the source states no known POP chain exists in the vulnerable plugin itself.
Likely exposure
Exposure is limited to WordPress installations running Advanced AJAX Product Filters <= 3.1.9.6 with Live Composer installed and active. Risk increases if untrusted users have Author-level access or if other installed plugins/themes contain exploitable POP chains.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires authenticated Author-level access or higher. Impact may include file deletion, sensitive data retrieval, or code execution only if a suitable POP chain exists elsewhere.
Researcher notes
The key uncertainty is exploitability in real deployments. The vulnerable plugin reportedly lacks its own POP chain, so validation should focus on prerequisite state and companion plugin/theme gadget availability without assuming universal code execution.
Mitigation direction
- Identify sites running Advanced AJAX Product Filters <= 3.1.9.6.
- Check whether Live Composer is installed and active.
- Update Advanced AJAX Product Filters if a vendor-fixed version is available.
- Remove or disable Live Composer if not required.
- Restrict Author-level access to trusted accounts only.
- Review vendor and Wordfence guidance for confirmed fixed versions.
Validation and detection
- Inventory WordPress sites for the affected plugin and version.
- Confirm whether Live Composer is active on each site.
- Review user accounts with Author-level or higher privileges.
- Audit installed plugins and themes for known PHP object injection gadget risks.
- Check plugin changelog or WordPress Trac changeset for remediation status.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1426 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/29e76d57-217f-4f21-8bc6-a86290783a19?source=cveCVE reference
- https://cwe.mitre.org/data/definitions/502.htmlCVE reference
- https://plugins.trac.wordpress.org/browser/woocommerce-ajax-filters/trunk/includes/compatibility/live_composer.php#L25CVE reference
- https://plugins.trac.wordpress.org/changeset/3449344/#file418CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
