Skip to main content

Booster for WooCommerce CVE-2026-42718

| EUVDEUVD-2026-96450 CRITICAL
Deserialization of Untrusted Data (CWE-502)
2026-10-10 Patchstack GHSA-3777-f2vm-752j
9.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach public WooCommerce endpoint
  2. Delivery
    Submit crafted serialized PHP object
  3. Exploit
    Trigger unsafe unserialize() in plugin
  4. Execution
    Invoke POP gadget chain
  5. Impact
    Execute code / compromise site

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the target to be running Booster for WooCommerce (plugin slug woocommerce-jetpack, vendor pluggabl) at version 8.4.0 or earlier on a WordPress/WooCommerce site that is network-reachable. The CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction, and no non-default configuration are needed, so default installs of the affected versions are exposed. Practical impact is limited by whether a usable PHP POP gadget chain is reachable in the plugin or other loaded code at the point of unserialization; without such a chain, object injection may not escalate to full code execution. Primary limiting factor is simply having the affected plugin version installed and the site internet-facing.

Impact

The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8 Critical) describes a remotely reachable, low-complexity, unauthenticated flaw with full confidentiality, integrity and availability impact - consistent with a CWE-502 PHP Object Injection that typically yields remote code execution when a usable POP gadget chain is present. However, several corroborating signals are absent: no EPSS exploitation-probability score was provided, the vulnerability is NOT listed in CISA KEV, and no public POC/exploit code is referenced. The single source is a Patchstack advisory, so exploitation status is 'no public exploit identified at time of analysis' - the high CVSS reflects worst-case potential (deserialization of attacker-controlled data) rather than confirmed in-the-wild activity. A key caveat for PHP Object Injection specifically: real-world impact depends on whether an exploitable gadget chain exists in the plugin or co-loaded code; without that, the practical outcome may be limited to object instantiation rather than full RCE, which the raw 9.8 does not capture. Net: treat as a genuine high priority for WooCommerce operators running the affected plugin (unauthenticated + network reachable), but note that EPSS/KEV/POC corroboration is missing, so widespread automated exploitation is not yet evidenced.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to a public-facing WooCommerce store running Booster for WooCommerce <= 8.4.0, embedding a serialized PHP object in a parameter the plugin deserializes. If a suitable gadget chain is reachable, the injected object triggers unintended code paths during unserialization, potentially leading to remote code execution, data disclosure, or site compromise. No authentication or user interaction is required (PR:N/UI:N), though no public exploit code is referenced at time of analysis.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 10, 2026

Unauthenticated PHP object injection in Booster for WooCommerce (WordPress plugin slug woocommerce-jetpack, vendor pluggabl) at version 8.4.0 and earlier allows remote attackers to feed attacker-controlled serialized data into the plugin's deserialization path on any internet-facing WordPress/WooCommerce site, with the assessed CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8 Critical) indicating no credentials, no user interaction, and no non-default configuration are required. Escalation to full remote code execution depends on whether a usable PHP POP gadget chain is reachable in the plugin or other loaded code at the point of unserialization, so the practical worst case is complete site compromise while the minimum case is a deserialization primitive with uncertain downstream effect. There is no public exploit identified at time of analysis and the issue is not listed in CISA KEV; Patchstack is credited as the reporter.

RemediationAI

No vendor-released patch version for this issue is identified in the provided data, so the actionable steps begin with confirming the installed Booster for WooCommerce version and either removing or deactivating the plugin (slug woocommerce-jetpack) on any site that does not strictly need it - the trade-off is loss of the storefront features it provides - or, if continued use is required, monitoring https://patchstack.com/database/wordpress/plugin/woocommerce-jetpack/vulnerability/wordpress-booster-for-woocommerce-plugin-8-4-0-php-object-injection-vulnerability?_s_id=cve and the vendor's WordPress.org plugin page for the fixed release and upgrading immediately when it is published. Compensating controls while unpatched: front the site with a WAF configured to detect and block serialized-object payloads (O: patterns and base64/URL-encoded equivalents) in query strings, POST bodies, cookies, and headers, understanding that encoding tricks can evade signatures and that false positives may break legitimate plugin traffic; restrict administrative and WooCommerce AJAX/REST endpoints to trusted source addresses where operationally feasible, accepting that this can break storefront functionality for legitimate customers; and keep WordPress core, WooCommerce, and all themes/plugins current to reduce the chance of a POP gadget chain being reachable. Because the flaw requires no authentication or user interaction, log review and integrity monitoring on affected installs is advisable, though success of such monitoring depends on the plugin's post-exploitation behavior, which is not described in the available data.

Affected VersionsENISA

Booster for WooCommerce n/a ≤8.4.0

Affected Packages

euvd booster_for_woocommerce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-502 (Deserialization of Untrusted Data): the plugin passes attacker-supplied input into a PHP unserialize()/object-instantiation sink without adequate validation or type restriction, allowing an attacker to construct arbitrary PHP objects. In the PHP object injection pattern, the attacker does not execute code directly; instead they supply a serialized object graph whose magic methods (__wakeup, __destruct, __toString, __call, and similar) are invoked automatically during unserialization, and those methods must chain through classes already loaded by the plugin, WordPress core, WooCommerce, or other active themes and plugins. The CPE cpe:2.3:a:pluggabl:booster_for_woocommerce:*:*:*:*:*:*:*:* with a wildcard version confirms that the affected vendor product is the pluggabl-published Booster for WooCommerce plugin and that the record covers the version range up to and including 8.4.0 rather than a single build. The vulnerability sits in the plugin's handling of request data on a standard PHP/WordPress stack, which is why the vector carries AC:L and PR:N: no special conditions or account are needed to reach the sink on a default installation. Impact therefore hinges on gadget availability rather than on the injection itself, and the provider's CVSS scores the confidentiality, integrity, and availability consequences as high on the assumption that such a chain exists.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Unauthenticated remote object injection (PR:N/AV:N/AC:L) in a web plugin with deserialization-to-RCE potential justifies C:H/I:H/A:H; scope unchanged as impact stays within the PHP application.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated PHP Object Injection in Booster for WooCommerce <= 8.4.0 versions.

Executive ViewAI

Why It Matters

Organizations running Booster for WooCommerce (woocommerce-jetpack) versions 8.4.0 and earlier on internet-facing WordPress/WooCommerce sites face a critical unauthenticated vulnerability that could result in complete site compromise in the worst case. Because these sites often handle customer data, payments, and order workflows, a compromise could disrupt revenue, expose sensitive information, and damage customer trust. Leadership should treat remediation as urgent while noting that no public exploit has been identified at time of analysis.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove Booster for WooCommerce (woocommerce-jetpack) version 8.4.0 and earlier; if removal is not feasible, restrict the plugin's exposure, deploy WAF/virtual patching rules to block serialized PHP object injection attempts, monitor WordPress and server logs for exploitation indicators, and isolate or back up affected sites.

Threat Intelligence Overview

EPSS Score
0.4%
Top 69% exploitable
Prevalence
Medium
popular WooCommerce plugin, common but not on every site
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy