Catch Themes Demo Import <= 3.3 - Missing Authorization to Authenticated (Subscriber+) Single Plugin Installation via 'activate_plugin' Parameter
Strategic Overview
- Status
- Patched in 3.4
- Affected Plugin
- Catch Themes Demo Import
- Affected Version
<= 3.3- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-15336
At a glance
CVE-2026-15336 is a medium-severity Missing Authorization vulnerability in the Catch Themes Demo Import WordPress plugin, affecting versions <= 3.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.4; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.
Vulnerability Overview
The Catch Themes Demo Import plugin for WordPress is vulnerable to Missing Authorization in versions up to, and including, 3.3. This is due to the catch_themes_demo_import_activate_plugin() function, hooked on admin_init when the activate_plugin GET parameter is present, calling Plugin_Upgrader::install() to download and install a plugin from WordPress.org before performing the current_user_can('activate_plugins') capability check. This makes it possible for authenticated attackers, with subscriber-level access and above, to install the hardcoded 'essential-content-types' plugin from the WordPress.
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
Catch Themes Demo Import <= 3.3 carries this weakness at activate_plugins, and reaching it takes an account at Subscriber level or above. 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 Catch Themes Demo Import the fix is 3.4: builds <= 3.3 are affected, anything from 3.4 onward is not.
Remediation
Update to version 3.4, 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: Catch Themes Demo Import 3.4 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Catch Themes Demo Import
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C