The WooCommerce Infinite Scroll and Ajax Pagination plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 1.8 via the 'settings' parameter in the 'import_settings' function. This is due to deserialization of untrusted data supplied via the import configuration feature without capability checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to inject a PHP Object. No POP chain is present within the vulnerable plugin itself, but if a POP chain is present via an additional plugin or theme installed on the target system, it could allow an attacker to delete arbitrary files, retrieve sensitive data, or execute code.
Security readout for executives and security teams
Plain-English summary
A WordPress WooCommerce add-on can let any logged-in user, even Subscriber-level, feed unsafe serialized data into an import settings feature. On its own, the plugin lacks the needed POP chain, but another installed plugin or theme could turn this into file deletion, data theft, or code execution.
Executive priority
Treat this as high priority for WooCommerce sites, especially stores allowing customer accounts. The issue requires authentication but may be reachable by ordinary registered users and could become severe in plugin-heavy WordPress environments.
Technical view
CVE-2025-11993 is CWE-502 PHP object injection in WooCommerce Infinite Scroll and Ajax Pagination through the settings parameter in import_settings. Sources attribute this to unsafe deserialization and missing capability checks in versions up to and including 1.8. CVSS 3.1 is 8.8 with low-privilege authenticated access required.
Likely exposure
Exposure is limited to WordPress sites running the affected WooCommerce Infinite Scroll and Ajax Pagination plugin version, with any Subscriber-or-higher account available to an attacker. Public-facing stores with customer registration are more exposed.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Practical impact depends on whether the target WordPress installation has another plugin or theme providing a usable POP chain.
Researcher notes
Evidence supports authenticated PHP object injection through import_settings and unsafe settings deserialization. The bundle says no POP chain exists in the vulnerable plugin itself. Affected-version metadata appears inconsistent, so rely on the narrative version range and vendor guidance.
Mitigation direction
Inventory WordPress sites for this plugin and versions up to 1.8.
Check vendor, marketplace, and Wordfence guidance for a fixed release.
Disable or remove the plugin where it is not business-critical.
Restrict untrusted Subscriber-level account creation until remediated.
Remove unused plugins and themes to reduce POP-chain exposure.
Monitor for suspicious settings import activity and unexpected file changes.
Validation and detection
Confirm installed plugin name and version on all WooCommerce sites.
Review whether public registration creates Subscriber-level accounts.
Check user lists for suspicious or recently created low-privilege accounts.
Review WordPress and web logs for unusual settings import requests.
Assess installed plugins and themes for known deserialization gadget risks.
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.
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
5Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
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.
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.