CVE-2026-15336 MEDIUM

CVE-2026-15336: Catch Themes Demo Import <= 3.3 - Missing Authorization to Authenticated (Subscriber+) Single Plugin Installation via 'activate_plugin' Parameter

Vendor Catchplugins
Product Catch Themes Demo Import
Weakness CWE-862 · Missing authorization
Published July 16, 2026
Last update July 16, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Catch Themes Demo Import versions 3.3 and earlier lack proper authorization checks, allowing authenticated users with low privileges to modify site content. An attacker with a basic user account can bypass intended access restrictions and alter data they should not be able to change. Update to a version newer than 3.3 to resolve this issue.

What an attacker can do

03Attacker Capabilities

Modify site content or settings that should be restricted to higher-privilege users.

Potential impact on your site

04Site Impact

Unauthorized users can alter site data, potentially corrupting demo imports or modifying site configuration.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site (e.g., subscriber or contributor role).

Key dates

06Disclosure timeline

July 16, 2026 CVE published

Related vulnerabilities

08Related CVE