Skip to main content

WooCommerce Designer Pro CVE-2026-32568

| EUVDEUVD-2026-93231 CRITICAL
Code Injection (CWE-94)
2026-10-06 Patchstack GHSA-37jp-c43x-pc4v
9.9
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Register or obtain Subscriber account
  2. Delivery
    Send crafted request to plugin endpoint
  3. Exploit
    Trigger PHP code injection (CWE-94)
  4. Execution
    Execute arbitrary code as web server
  5. Impact
    Full server/store compromise

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
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 a valid authenticated WordPress account at Subscriber level or higher (PR:L) on a site running WooCommerce Designer Pro <= 1.9.33; exploitation is most realistic on storefronts that permit open customer self-registration, which is common for WooCommerce. No administrative privileges and no user interaction are required (UI:N). The primary limiting factor is the authentication requirement - sites that disable public registration and have no low-privilege accounts raise the bar, though any compromised or malicious Subscriber still suffices. The exact vulnerable endpoint/feature is not detailed in the available description.

Impact

This is a genuine high-priority issue, not merely a high-CVSS paper tiger. The CVSS 9.9 rating is supported by a coherent vector: AV:N/AC:L/PR:L/UI:N/S:C with full C:H/I:H/A:H impact, describing code injection (CWE-94) that an authenticated Subscriber - the lowest WordPress privilege tier, trivially self-registered on many WooCommerce storefronts - can leverage into remote code execution with no user interaction and a scope change onto the host. The effective barrier to entry (a Subscriber account) is very low on a public e-commerce site that allows account registration, which is the common default. Counterbalancing this: no EPSS score, no CISA KEV listing, and no public POC were provided in the input, so there is no evidence of active exploitation or weaponized exploit code at this time - exploitation probability is currently unquantified rather than confirmed low. The sole source is a Patchstack advisory; there is no independent NVD/vendor corroboration in the supplied data. Net: treat as urgent-to-patch for any internet-facing store permitting self-registration, while recognizing that real-world exploitation signals (EPSS/KEV/POC) are simply absent, not negative.

Exploit ScenarioDerived

An attacker self-registers (or uses an existing Subscriber account) on a WooCommerce store running the vulnerable plugin, then sends a crafted request to an inadequately-restricted plugin endpoint that injects attacker-controlled code (CWE-94). Because PR:L and UI:N, no admin privileges or victim interaction are needed, and the scope change (S:C) means the injected code executes in the web server context, yielding full host compromise. No public exploit code was identified at time of analysis.

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

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

Alert me

AnalysisAIv1 – Oct 06, 2026

Remote code execution in WooCommerce Designer Pro (versions up to 1.9.33) allows authenticated attackers with Subscriber-level access or higher to execute arbitrary code on the server. The flaw is a code injection (CWE-94) with a CVSS score of 9.9 (Critical), requiring no user interaction and resulting in complete loss of confidentiality, integrity, and availability (scope change). Exploitation is most realistic on WooCommerce storefronts that permit open customer self-registration; no public exploit identified at time of analysis. The independent assessment confirms this is a genuine high-priority issue rather than a theoretical risk.

RemediationAI

No vendor-released patch is identified in the provided data; monitor the Patchstack advisory for an updated version. As an immediate workaround, consider disabling the WooCommerce Designer Pro plugin entirely if its design functionality is not critical-this removes the attack vector but eliminates the feature. If the plugin must remain active, disable public user registration to prevent untrusted users from obtaining Subscriber-level accounts; however, this may block legitimate customer sign-ups. Alternatively, restrict the Subscriber role's capabilities to the absolute minimum and audit existing Subscriber accounts for suspicious activity. Deploying a web application firewall (WAF) with rules targeting code injection patterns can provide temporary protection, but it is not a substitute for patching. Refer to the Patchstack advisory for further guidance: https://patchstack.com/database/wordpress/plugin/wc-designer-pro/vulnerability/wordpress-woocommerce-designer-pro-plugin-1-9-33-remote-code-execution-rce-vulnerability?_s_id=cve.

Affected VersionsENISA

WooCommerce Designer Pro n/a ≤1.9.33

Affected Packages

euvd woocommerce_designer_pro 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 vulnerability is a code injection flaw (CWE-94) in the WooCommerce Designer Pro WordPress plugin, which extends WooCommerce with product design capabilities. CWE-94 occurs when an application constructs code using externally influenced input without proper neutralization, often through functions like eval(), create_function(), or dynamic file inclusion. In this case, the plugin fails to adequately sanitize user-supplied data before using it in a code execution context, allowing an authenticated Subscriber to inject and execute arbitrary PHP code. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H) indicates network exploitability, low attack complexity, low privileges required (Subscriber), no user interaction, and a scope change that impacts the entire host. The affected product is identified by CPE 2.3:a:jmaplugins:woocommerce_design_pro:*:*:*:*:*:*:*:*, covering all versions up to and including 1.9.33. The plugin is developed by JMA Plugins and integrates with WordPress and WooCommerce, both of which run on PHP.

Know when Woocommerce Designer Pro 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.9 CRITICAL
AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
vuln.today AI 9.9 CRITICAL

Network-reachable code injection exploitable by a low-privilege Subscriber (PR:L) without interaction; injected code escapes the app to the host (S:C) giving full C/I/A impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Subscriber Remote Code Execution (RCE) in WooCommerce Designer Pro <= 1.9.33 versions.

Executive ViewAI

Why It Matters

WooCommerce Designer Pro (up to version 1.9.33) contains a critical remote code execution flaw that can lead to full compromise of an affected online store. No vendor-released patch identified at time of analysis, and exploitation is most realistic on storefronts with open customer self-registration, so leadership should treat this as an urgent business continuity and data protection risk. Affected organizations may face loss of customer data, payment disruption, and reputational damage if the plugin remains exposed.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include disabling WooCommerce Designer Pro if it is not essential, disabling open customer self-registration, restricting Subscriber-level account creation and capabilities, enforcing least privilege and MFA for administrative users, deploying WAF/virtual patching rules for CWE-94 code injection, and monitoring storefront and server logs for suspicious activity.

Threat Intelligence Overview

EPSS Score
0.7%
Top 47% exploitable
Prevalence
Low
niche commercial WooCommerce design plugin, limited install base
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.7%
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
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
Very High
Technical Impact
Total

Priority Score

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

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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