dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-11993

HIGH · 8.8 CVSS v3.1 Published 2026-05-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PHP Object Injection vulnerability in WooCommerce Infinite Scroll and Ajax Pagination plugin (versions up to 1.8) via the 'settings' parameter in the 'import_settings' function. The plugin deserializes untrusted data without proper input validation, allowing authenticated attackers with Subscriber-level access to inject arbitrary PHP objects. While no POP chain exists within the plugin itself, one could be leveraged from other plugins/themes present on the WordPress installation.

MitigationUpdate the plugin to version 1.8.1 or later. If no update is available, disable and remove the plugin immediately. Additionally, audit the WordPress installation for other plugins or themes that may provide a POP chain for object injection exploitation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    Locate the plugin directory (typically wp-content/plugins/woocommerce-infinite-scroll-and-ajax-pagination or similar) and check the main plugin file header for the Version field, or query via WordPress admin plugins list
    Affected if The plugin is installed and the version falls within the affected range (prior to the patched release)
  2. Verify plugin activation status
    Check WordPress admin under Plugins > Installed Plugins to confirm the WooCommerce Infinite Scroll and Ajax Pagination plugin is active
    Affected if The plugin is active and vulnerable version is installed
  3. Confirm user registration or subscriber access is enabled
    In WordPress admin under Settings > General, check if 'Anyone can register' is enabled and if the default role is set to Subscriber, or review existing user accounts with Subscriber role
    Affected if Subscriber-level accounts exist or can be registered, enabling authenticated access to the vulnerable import_settings function
  4. Test import_settings endpoint accessibility
    Check if the AJAX action handling import_settings (typically hooked to wp_ajax_isp_import_settings or similar) is registered without a capability check (such as manage_options). Review the plugin source code for the add_action call and the capability requirement in the callback
    Affected if The import_settings function is exposed without capability verification, allowing any authenticated user (including Subscriber) to trigger deserialization of the settings parameter
  5. Identify potential POP chain sources
    Audit all other installed plugins and the active theme for known PHP Object Injection POP chains or unserialize() calls that could be chained with this vulnerability
    Affected if Other vulnerable plugins/themes with exploitable POP chains are installed, allowing arbitrary object injection to achieve RCE or file operations

The environment is affected if the WooCommerce Infinite Scroll and Ajax Pagination plugin is installed in a vulnerable version, is active, and the import_settings functionality is exposed to authenticated users without proper capability checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to version 1.8.1 or later. If no update is available, disable and remove the plugin immediately. Additionally, audit the WordPress installation for other plugins or themes that may provide a POP chain for object injection exploitation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11993 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11993 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data