LiveActive security incident?Get immediate response
CVE Record

CVE-2026-1426: Advanced AJAX Product Filters <= 3.1.9.6 - Authenticated (Author+) PHP Object Injection via Live Composer Compatibility

The Advanced AJAX Product Filters plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.1.9.6 via deserialization of untrusted input in the shortcode_check function within the Live Composer compatibility layer. This makes it possible for authenticated attackers, with Author-level access and above, 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. Note: This vulnerability requires the Live Composer plugin to also be installed and active.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

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.
Prepared
Confidence
medium
Sources
8

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

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 lookup
cve · low confidence lookup

CVE-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
Vulnerability profileCVE Program record
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

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2026-1426Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
berocketAdvanced AJAX Product Filters0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-502 · source CWE mapping

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.