Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-111847 Overview
CVE-2026-111847 is a missing authorization vulnerability in the Kings Plugins MarketKing multivendor marketplace plugin for WooCommerce. The flaw affects all versions from an unspecified initial release through 2.1.72. An authenticated attacker with low-level privileges can exploit incorrectly configured access control checks to perform actions outside their intended permission scope. The vulnerability is tracked under CWE-862: Missing Authorization and is published in the Patchstack Vulnerability Report.
Critical Impact
Authenticated users can bypass access control checks to read or modify data within MarketKing-powered WooCommerce marketplaces, affecting both confidentiality and integrity.
Affected Products
- Kings Plugins MarketKing (marketking-multivendor-marketplace-for-woocommerce)
- MarketKing versions through 2.1.72
- WordPress sites running WooCommerce with the vulnerable MarketKing plugin
Discovery Timeline
- 2026-10-22 - CVE-2026-111847 published to NVD
- 2026-10-22 - Last updated in NVD database
Technical Details for CVE-2026-111847
Vulnerability Analysis
MarketKing extends WooCommerce with multivendor marketplace functionality, exposing numerous administrative and vendor-facing endpoints. The plugin fails to enforce authorization checks on one or more of these endpoints. As a result, a user authenticated with low privileges can invoke functionality intended for higher-privileged roles such as marketplace administrators or other vendors.
The vulnerability falls under broken access control, specifically the pattern described by CWE-862. The code paths involved perform a requested action without first verifying that the current user holds the capability or ownership required for that action.
The attack can be performed over the network against the WordPress HTTP interface, requires low attack complexity, and needs only low-privileged authentication. No user interaction is required. The impact includes limited disclosure and limited modification of data, with no direct denial of service.
Root Cause
The root cause is a missing or insufficient authorization check within handlers exposed by the MarketKing plugin. WordPress plugins typically protect privileged actions using current_user_can() capability checks and nonce verification through check_ajax_referer() or wp_verify_nonce(). When these guards are omitted on request handlers, any authenticated user who can reach the endpoint can trigger the underlying action.
Attack Vector
An attacker needs a valid low-privileged account on the target WordPress site, such as a customer or vendor account on the marketplace. The attacker crafts an HTTP request to the vulnerable MarketKing endpoint and submits it directly, bypassing the user interface controls that normally restrict visibility of these actions. The server processes the request without validating the caller's role, returning data or committing changes that should have been restricted.
The vulnerability manifests in request handlers that lack capability checks. See the Patchstack Vulnerability Report for additional technical details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-111847
Indicators of Compromise
- Unexpected modifications to vendor products, orders, commissions, or payout settings not tied to administrator activity.
- HTTP requests from low-privileged user sessions to MarketKing AJAX actions (admin-ajax.php?action=marketking_*) or REST routes they would not normally invoke.
- Access log entries showing non-admin accounts hitting endpoints associated with vendor or administrator management.
Detection Strategies
- Review WordPress and web server access logs for requests to MarketKing endpoints originating from accounts without the corresponding role.
- Correlate authenticated session identifiers against actions performed in the WooCommerce and MarketKing database tables to detect privilege mismatches.
- Monitor for anomalous spikes in requests to admin-ajax.php or MarketKing REST endpoints shortly after new account registration.
Monitoring Recommendations
- Enable detailed WordPress audit logging for role changes, product edits, order modifications, and vendor configuration changes.
- Forward web server, WordPress, and WooCommerce logs to a centralized analytics platform for correlation and retention.
- Alert on any 200-status responses to MarketKing administrative actions where the authenticated user is not an administrator or the owning vendor.
How to Mitigate CVE-2026-111847
Immediate Actions Required
- Upgrade the MarketKing plugin to a version later than 2.1.72 once a vendor-supplied patch is published.
- Audit existing marketplace data for unauthorized changes to vendor accounts, products, orders, and payout configurations.
- Rotate credentials for any accounts suspected of being abused and review recently created low-privileged accounts.
Patch Information
MarketKing versions through 2.1.72 are affected. Refer to the Patchstack Vulnerability Report and the Kings Plugins vendor channel for the fixed version. Apply the update through the WordPress plugin manager or by replacing the plugin files directly.
Workarounds
- Restrict access to the WordPress admin and AJAX endpoints with a web application firewall rule that blocks non-administrator requests to MarketKing administrative actions.
- Temporarily disable the MarketKing plugin on sites that cannot be patched immediately and do not depend on live marketplace functionality.
- Limit new user registrations and require manual approval for vendor accounts until the plugin is updated.
# Example: block low-privileged access to MarketKing admin-ajax actions at the web server
# (NGINX location snippet - adjust the action pattern to match your deployment)
location = /wp-admin/admin-ajax.php {
if ($arg_action ~* "^marketking_") {
# Require an authenticated admin session cookie before proxying
if ($http_cookie !~* "wordpress_logged_in_admin") {
return 403;
}
}
include fastcgi_params;
fastcgi_pass php_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

