CVE-2025-11993
Deferred Deferred - Pending Action
PHP Object Injection in WooCommerce Infinite Scroll and Ajax Pagination Plugin

Publication date: 2026-05-29

Last updated on: 2026-05-29

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-29
Last Modified
2026-05-29
Generated
2026-05-29
AI Q&A
2026-05-29
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
sbthemes woocommerce_infinite_scroll_and_ajax_pagination to 1.8 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

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. This vulnerability arises because the plugin deserializes untrusted data supplied via the 'settings' parameter in the 'import_settings' function without performing capability checks.

Authenticated attackers with Subscriber-level access or higher can exploit this flaw to inject a PHP Object. Although the vulnerable plugin itself does not contain a POP (Property Oriented Programming) chain, if another plugin or theme installed on the system has such a chain, the attacker could leverage it to delete arbitrary files, retrieve sensitive data, or execute arbitrary code.


How can this vulnerability impact me? :

This vulnerability can have severe impacts including the potential for an attacker to delete arbitrary files, retrieve sensitive information, or execute arbitrary code on the affected system.

Since the attack requires only Subscriber-level access, it lowers the barrier for exploitation, making it easier for less privileged users to cause significant harm.

The overall impact includes confidentiality, integrity, and availability being compromised, as reflected by the high CVSS score of 8.8.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability exists in the WooCommerce Infinite Scroll and Ajax Pagination plugin for WordPress, specifically in versions up to and including 1.8. Detection involves identifying if this plugin and vulnerable version is installed on your WordPress site.

You can detect the presence of the vulnerable plugin and version by checking the installed plugins list in WordPress or by inspecting the plugin files on the server.

  • Use WP-CLI to list installed plugins and their versions: wp plugin list
  • Check the plugin directory for the version file or readme.txt to confirm the version.
  • Look for suspicious HTTP requests targeting the 'import_settings' function or the 'settings' parameter, which could indicate exploitation attempts.
  • Monitor web server logs for POST requests containing 'import_settings' or unusual serialized PHP objects in parameters.

What immediate steps should I take to mitigate this vulnerability?

The primary mitigation step is to update the WooCommerce Infinite Scroll and Ajax Pagination plugin to a version later than 1.8 where this vulnerability is fixed.

If an update is not immediately available, consider disabling or removing the plugin to prevent exploitation.

Restrict access to the import configuration feature to trusted users only, as the vulnerability requires authenticated access at Subscriber level or above.

Implement web application firewall (WAF) rules to block requests attempting to exploit the 'import_settings' function or containing suspicious serialized data.

Regularly monitor logs for exploitation attempts and unauthorized access.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows authenticated attackers with Subscriber-level access and above to perform PHP Object Injection via deserialization of untrusted data without capability checks. This could potentially lead to deletion of arbitrary files, retrieval of sensitive data, or code execution if a POP chain is present through other plugins or themes.

Such unauthorized access and potential data exposure or manipulation could impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding sensitive data and ensuring system integrity.

However, the provided information does not explicitly detail the compliance impact or specific regulatory consequences.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart