dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-12349

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 7 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Premium Addons for KingComposer plugin exposes add_custom_sidebar() and remove_custom_sidebar() AJAX handlers via wp_ajax_nopriv_* hooks, making them accessible to unauthenticated users. These functions directly write to the octagon_custom_sidebar option via update_option() without any capability checks or authorization validation, allowing attackers to create or delete arbitrary custom widget areas.

MitigationAdd capability checks (e.g., current_user_can('manage_options')) and nonce verification to both AJAX handlers, and migrate from wp_ajax_nopriv_* to wp_ajax_* hooks to require authentication.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation and version
    Check if Premium Addons for KingComposer plugin is installed in wp-content/plugins/ and retrieve its version from the plugin header comment in the main PHP file
    Affected if The plugin is installed and your version falls within any affected version range (compare your installed version to the affected ranges)
  2. Identify vulnerable AJAX endpoint accessibility
    Send a POST request to wp-admin/admin-ajax.php with action=add_custom_sidebar or action=remove_custom_sidebar without providing authentication cookies or a valid nonce
    Affected if The request succeeds and returns a successful response (HTTP 200) indicating the AJAX handler executes without authentication requirements
  3. Verify option modification capability
    Check if the octagon_custom_sidebar option in wp_options table can be modified by triggering the AJAX handlers without proper capability checks
    Affected if The AJAX handlers execute update_option() calls on octagon_custom_sidebar without verifying current_user_can('manage_options') or validating a nonce
  4. Inspect hook registration for the vulnerable handlers
    Examine the plugin source code for wp_ajax_nopriv_add_custom_sidebar and wp_ajax_nopriv_remove_custom_sidebar hook registrations
    Affected if These hooks are registered with wp_ajax_nopriv_* prefix, making them accessible to unauthenticated users

You are affected if the Premium Addons for KingComposer plugin is installed with a vulnerable version AND the AJAX endpoints add_custom_sidebar/remove_custom_sidebar are accessible without authentication (via wp_ajax_nopriv_* hooks).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Add capability checks (e.g., current_user_can('manage_options')) and nonce verification to both AJAX handlers, and migrate from wp_ajax_nopriv_* to wp_ajax_* hooks to require authentication.

Recommended fix Moderate confidence

Premium Addons for KingComposer version 1.1.2 or latest available version

  1. Check current version of Premium Addons for KingComposer plugin in WordPress admin under Plugins > Installed Plugins
  2. If running version 1.1.1 or lower, navigate to Plugins > Add New > Upload Plugin or check the plugin's update mechanism
  3. Update to the latest available version of Premium Addons for KingComposer (version 1.1.2 or later)
  4. Verify the update was successful by confirming the new version number
  5. Test that custom sidebar functionality still works correctly after the update

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-12349 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-12349 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data