CVE-2026-57329
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 · uneditedSubscriber Cross Site Scripting (XSS) in WooCommerce Designer Pro <= 1.9.34 versions.
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 confidenceA stored Cross Site Scripting (XSS) vulnerability exists in WooCommerce Designer Pro plugin versions 1.9.34 and below. The flaw allows authenticated subscribers to inject malicious JavaScript code through plugin inputs that is then executed in the browsers of other users who view the injected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if WooCommerce Designer Pro is installedIn WordPress admin, navigate to Plugins > Installed Plugins and look for 'WooCommerce Designer Pro' or 'Designer Pro' in the list. Alternatively, check the /wp-content/plugins/ directory for a folder named similarly to 'designer-pro' or 'woocommerce-designer-pro'.Affected if The plugin is found and active in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin > Plugins, click on the plugin name to view its details, or check the plugin's main PHP file for a 'Version' comment/header. Compare this version number against the affected range (1.9.34 and below).Affected if The installed version is 1.9.34 or any lower version number
-
Check for subscriber-level user accountsIn WordPress admin, go to Users > All Users and review the 'Role' column. Look for any users assigned the 'Subscriber' role. XSS exploitation requires an authenticated user with subscriber-level access or higher.Affected if At least one user account with Subscriber role (or higher) exists on the site
-
Inspect plugin input fields for existing malicious contentNavigate to the WooCommerce Designer Pro plugin settings pages where users can submit or save content (such as design templates, product customizations, or text inputs). View the page source or use the browser developer tools to examine if any stored content contains unsanitized script tags, event handlers (onclick, onerror, etc.), or suspicious encoded strings.Affected if Unexpected script tags, javascript: URIs, or HTML event attributes are found in stored plugin content that was not intentionally added by an administrator
Your environment is affected if WooCommerce Designer Pro is installed with version 1.9.34 or lower AND any subscriber-level or higher user account exists on the site.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate WooCommerce Designer Pro to a version higher than 1.9.34 when a patched release becomes available. Until then, limit subscriber permissions and monitor for suspicious user activity.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57329 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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