CVE-2026-12349 MEDIUM

CVE-2026-12349: Premium Addons for KingComposer <= 1.1.1 - Missing Authorization to Unauthenticated Arbitrary Custom Sidebar Creation and Deletion via 'add_custom_sidebar' and 'remove_custom_sidebar' AJAX actions

Vendor Octagonwebstudio
Product Premium Addons for KingComposer
Weakness CWE-862 · Missing authorization
Published June 30, 2026
Last update June 30, 2026

CVSS base score

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

CVSS vector

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

What the vulnerability does

01Description

The Premium Addons for KingComposer plugin for WordPress is vulnerable to unauthorized modification and loss of data in versions up to, and including, 1.1.1. This is due to missing authorization and capability checks on the add_custom_sidebar() and remove_custom_sidebar() AJAX handlers, both of which are exposed through wp_ajax_nopriv_* hooks and write directly to the octagon_custom_sidebar option via update_option(). This makes it possible for unauthenticated attackers to create arbitrary custom widget areas or delete existing custom sidebars, which can cause widgets assigned to those areas to silently lose their registration and stop rendering.

Explanation of Vulnerability in Simple Terms

02Summary

Premium Addons for KingComposer versions 1.1.1 and earlier lack proper authorization checks, allowing unauthenticated attackers to modify site content or settings. The vulnerability requires only network access and no user interaction. Site administrators should update to a version newer than 1.1.1 immediately.

What an attacker can do

03Attacker Capabilities

Modify site content or settings without logging in.

Potential impact on your site

04Site Impact

Unauthorized changes to site content, settings, or data integrity without any warning or audit trail.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

June 30, 2026 CVE published