CVE-2025-9029

WDesignKit – Elementor & Gutenberg Starter Templates, Patterns, Cloud Workspace & Widget Builder <= 1.2.16 - Missing Authentication via wdkit_handle_review_submission Function

2025-10-03 14:09
Peter Thaleikis

Strategic Overview

Status
Patched in 1.2.17
Affected Version
<= 1.2.16
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2025-9029
View all WDesignKit – AI Templates, Widget Builder & MCP Workflow for WordPress vulnerabilities

At a glance

CVE-2025-9029 is a medium-severity Missing Authorization vulnerability in the WDesignKit WordPress plugin, affecting versions <= 1.2.16. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.17; sites on affected versions should update now. Disclosed October 2025, reported by Peter Thaleikis.

Vulnerability Overview

The WDesignKit – Elementor & Gutenberg Starter Templates, Patterns, Cloud Workspace & Widget Builder plugin for WordPress is vulnerable to missing authorization via the wdkit_handle_review_submission function in versions less than, or equal to, 1.2.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to submit feedback data to external services.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WDesignKit <= 1.2.16 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WDesignKit the fix is 1.2.17: builds <= 1.2.16 are affected, anything from 1.2.17 onward is not.

Remediation

Update to version 1.2.17, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WDesignKit 1.2.17 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Other vulnerabilities in WDesignKit – AI Templates, Widget Builder & MCP Workflow for WordPress

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C