Skip to content
major vulnerability· requires attention

Extremely popular WordPress plugin with potential to impact many e-commerce sites; exploitation could disrupt business operations.

Web

CVE-2025-11993

8.8
High
EPSS 0.38%Patch availableMay 29, 2026

PHP Object Injection in WooCommerce Infinite Scroll (<=1.8) via import_settings.

common questions

Is CVE-2025-11993 being exploited?

Not confirmed. CVE-2025-11993 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.38% probability of exploitation in the next 30 days.

How severe is CVE-2025-11993?

CVE-2025-11993 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-2025-11993?

Yes. A fix has been recorded for CVE-2025-11993. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-11993 affect?

CVE-2025-11993 affects WordPress plugin: WooCommerce Infinite Scroll and Ajax Pagination (<=1.8). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-11993?

Update to latest plugin version; review and limit import_settings access.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress plugin: WooCommerce Infinite Scroll and Ajax Pagination (<=1.8)
impact

Authenticated Subscriber+ can inject PHP objects; may delete files, access data, or execute code if a POP chain exists.

action required

Patch when possible

affected versions
sbthemes WooCommerce Infinite Scroll and Ajax Pagination
  • affected<= 1.8

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free