Stylemixmes Motors Plugin up to 5.6.80 on WordPress authorization

Summaryinfo

A vulnerability identified as critical has been detected in Stylemixmes Motors Plugin up to 5.6.80 on WordPress. Impacted is an unknown function. This manipulation causes authorization. This vulnerability appears as CVE-2026-27433. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Stylemixmes Motors Plugin up to 5.6.80 on WordPress and classified as critical. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect integrity, and availability. The summary by CVE is:

Unauthenticated Broken Access Control in Motors <= 5.6.80 versions.

The weakness was presented by Rafie Muhammad. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2026-27433 since 02/19/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/02/2026).

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

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• WordPress Plugin

Vendor

• Stylemixmes

Name

• Motors Plugin

Version

• 5.6.0
• 5.6.1
• 5.6.2
• 5.6.3
• 5.6.4
• 5.6.5
• 5.6.6
• 5.6.7
• 5.6.8
• 5.6.9
• 5.6.10
• 5.6.11
• 5.6.12
• 5.6.13
• 5.6.14
• 5.6.15
• 5.6.16
• 5.6.17
• 5.6.18
• 5.6.19
• 5.6.20
• 5.6.21
• 5.6.22
• 5.6.23
• 5.6.24
• 5.6.25
• 5.6.26
• 5.6.27
• 5.6.28
• 5.6.29
• 5.6.30
• 5.6.31
• 5.6.32
• 5.6.33
• 5.6.34
• 5.6.35
• 5.6.36
• 5.6.37
• 5.6.38
• 5.6.39
• 5.6.40
• 5.6.41
• 5.6.42
• 5.6.43
• 5.6.44
• 5.6.45
• 5.6.46
• 5.6.47
• 5.6.48
• 5.6.49
• 5.6.50
• 5.6.51
• 5.6.52
• 5.6.53
• 5.6.54
• 5.6.55
• 5.6.56
• 5.6.57
• 5.6.58
• 5.6.59
• 5.6.60
• 5.6.61
• 5.6.62
• 5.6.63
• 5.6.64
• 5.6.65
• 5.6.66
• 5.6.67
• 5.6.68
• 5.6.69
• 5.6.70
• 5.6.71
• 5.6.72
• 5.6.73
• 5.6.74
• 5.6.75
• 5.6.76
• 5.6.77
• 5.6.78
• 5.6.79
• 5.6.80

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion