CVE-2026-14357 HIGH

CVE-2026-14357: DevKit Pro <= 2.3.0 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Theme Installation / Remote Code Execution via 'qqfile' Parameter

Vendor Dplugins
Product DevKit Pro
Weakness CWE-862 · Missing authorization
Published September 2, 2026
Last update September 2, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The DevKit Pro plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 2.3.0. This is due to a missing capability check and missing nonce validation in the DPDEV_install_themes_func() function registered on the wp_ajax_DPDEV_install_themes action. This makes it possible for authenticated attackers, with Subscriber-level access and above, to install arbitrary theme ZIP packages containing PHP files that are extracted into the web-accessible wp-content/themes/ directory, which may make remote code execution possible.

Explanation of Vulnerability in Simple Terms

02Summary

DevKit Pro versions 2.3.0 and earlier lack proper authorization checks, allowing authenticated users with low privileges to read, modify, or delete sensitive data and functionality. An attacker with a basic user account can perform actions restricted to administrators without additional authentication. This affects all data and operations within the plugin.

What an attacker can do

03Attacker Capabilities

Read, modify, or delete sensitive data and perform admin-level actions with a low-privilege user account.

Potential impact on your site

04Site Impact

Any registered user can access and modify critical plugin settings, data, and functionality intended only for administrators.

Conditions required to exploit

05Prerequisites

Attacker must have a valid low-privilege user account on the site; no additional user interaction required.

Key dates

06Disclosure timeline

September 2, 2026 CVE published

Related vulnerabilities

08Related CVE