WebWizards MarketKing Plugin up to 2.1.70 on WordPress access control

Summaryinfo

A vulnerability marked as problematic has been reported in WebWizards MarketKing Plugin up to 2.1.70. This affects an unknown part. This manipulation causes access control. This vulnerability is tracked as CVE-2026-94080. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in WebWizards MarketKing Plugin up to 2.1.70. It has been declared as problematic. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity. The summary by CVE is:

Unauthenticated Broken Access Control in MarketKing <= 2.1.70 versions.

It is possible to read the advisory at patchstack.com. This vulnerability is known as CVE-2026-94080 since 09/20/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/23/2026). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• WebWizards

Name

• MarketKing Plugin

Version

• 2.1.0
• 2.1.1
• 2.1.2
• 2.1.3
• 2.1.4
• 2.1.5
• 2.1.6
• 2.1.7
• 2.1.8
• 2.1.9
• 2.1.10
• 2.1.11
• 2.1.12
• 2.1.13
• 2.1.14
• 2.1.15
• 2.1.16
• 2.1.17
• 2.1.18
• 2.1.19
• 2.1.20
• 2.1.21
• 2.1.22
• 2.1.23
• 2.1.24
• 2.1.25
• 2.1.26
• 2.1.27
• 2.1.28
• 2.1.29
• 2.1.30
• 2.1.31
• 2.1.32
• 2.1.33
• 2.1.34
• 2.1.35
• 2.1.36
• 2.1.37
• 2.1.38
• 2.1.39
• 2.1.40
• 2.1.41
• 2.1.42
• 2.1.43
• 2.1.44
• 2.1.45
• 2.1.46
• 2.1.47
• 2.1.48
• 2.1.49
• 2.1.50
• 2.1.51
• 2.1.52
• 2.1.53
• 2.1.54
• 2.1.55
• 2.1.56
• 2.1.57
• 2.1.58
• 2.1.59
• 2.1.60
• 2.1.61
• 2.1.62
• 2.1.63
• 2.1.64
• 2.1.65
• 2.1.66
• 2.1.67
• 2.1.68
• 2.1.69
• 2.1.70

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion