dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-27045

HIGH · 8.8 CVSS v3.1 Published 2026-03-25
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
Deserialization of Untrusted Data vulnerability in sbthemes WooCommerce Infinite Scroll sb-woocommerce-infinite-scroll allows Object Injection.This issue affects WooCommerce Infinite Scroll: from n/a through <= 1.6.2.

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 · moderate confidence

The WooCommerce Infinite Scroll plugin (sb-woocommerce-infinite-scroll) <= 1.6.2 contains a deserialization vulnerability (CWE-502) that allows attackers to inject malicious PHP objects by passing untrusted serialized data, potentially leading to remote code execution via object injection attacks.

MitigationUpgrade to a patched version of the plugin immediately. If no patch is available, disable the plugin until a secure version is released. Consider implementing object unserialize() whitelist filtering or replacing unsafe deserialization with json_decode().

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. Locate the WooCommerce Infinite Scroll plugin
    Check your WordPress site's wp-content/plugins/ directory for a folder named 'sb-woocommerce-infinite-scroll' or 'woocommerce-infinite-scroll', or look for it in the WordPress admin under Plugins > Installed Plugins
    Affected if The plugin folder exists in the plugins directory
  2. Identify the installed plugin version
    If the plugin folder exists, open the main PHP file (usually named something like sb-woocommerce-infinite-scroll.php) and look for a 'Version:' comment in the file header, or check the WordPress plugin admin page for the version number
    Affected if The installed version is 1.6.2 or lower
  3. Check for vulnerable deserialization code
    Search the plugin files for usage of unserialize() function without prior sanitization. Look for calls like unserialize($_POST['...']), unserialize($_GET['...']), or unserialize($_COOKIE['...']) in the plugin's PHP files, particularly in ajax handlers or frontend-facing files
    Affected if The plugin contains unserialize() calls that process untrusted input without validation
  4. Determine if the plugin endpoints are web-accessible
    Check if the plugin registers any REST API routes, AJAX actions, or query variables that could accept serialized data. Look for add_action calls like 'wp_ajax_' or 'wp_ajax_nopriv_' prefixed with the plugin's text domain, or check for any exposed endpoints in the site's HTTP responses
    Affected if The plugin exposes AJAX or API endpoints that handle serialized data without authentication or validation

Your environment is affected if the WooCommerce Infinite Scroll plugin is installed, the version is 1.6.2 or lower, and the plugin contains unserialize() handling of untrusted input that is accessible via web requests.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of the plugin immediately. If no patch is available, disable the plugin until a secure version is released. Consider implementing object unserialize() whitelist filtering or replacing unsafe deserialization with json_decode().

Recommended fix Moderate confidence

Latest available version from WordPress plugin repository or vendor (contact vendor for fixed release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'WooCommerce Infinite Scroll' (sb-woocommerce-infinite-scroll) plugin
  4. 4. Check the current installed version in the plugin details
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Verify the update was successful by checking the new version number
  7. 7. Test the infinite scroll functionality on the WooCommerce product pages to ensure normal operation
  8. 8. If no update is available in the WordPress plugin repository, contact the plugin vendor (sbthemes) directly to request the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27045 — 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-2026-27045 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