Azexo Marketing Automation Plugin up to 1.27.80 on WordPress privileges assignment

Summaryinfo

A vulnerability classified as critical was found in Azexo Marketing Automation Plugin up to 1.27.80 on WordPress. This issue affects some unknown processing. Such manipulation leads to privileges assignment. This vulnerability is documented as CVE-2024-50506. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Azexo Marketing Automation Plugin up to 1.27.80 on WordPress and classified as critical. Affected by this issue is an unknown function. The manipulation with an unknown input leads to a privileges assignment vulnerability. Using CWE to declare the problem leads to CWE-266. A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Incorrect Privilege Assignment vulnerability in Azexo Marketing Automation by AZEXO allows Privilege Escalation.This issue affects Marketing Automation by AZEXO: from n/a through 1.27.80.

The weakness was released by Bonds. The advisory is available at patchstack.com. This vulnerability is handled as CVE-2024-50506 since 10/24/2024. The exploitation is known to be easy. The attack may be launched remotely. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 10/30/2024). This vulnerability is assigned to T1068 by the MITRE ATT&CK project.

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 best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Automation Software

Vendor

• Azexo

Name

• Marketing Automation Plugin

Version

• 1.27.0
• 1.27.1
• 1.27.2
• 1.27.3
• 1.27.4
• 1.27.5
• 1.27.6
• 1.27.7
• 1.27.8
• 1.27.9
• 1.27.10
• 1.27.11
• 1.27.12
• 1.27.13
• 1.27.14
• 1.27.15
• 1.27.16
• 1.27.17
• 1.27.18
• 1.27.19
• 1.27.20
• 1.27.21
• 1.27.22
• 1.27.23
• 1.27.24
• 1.27.25
• 1.27.26
• 1.27.27
• 1.27.28
• 1.27.29
• 1.27.30
• 1.27.31
• 1.27.32
• 1.27.33
• 1.27.34
• 1.27.35
• 1.27.36
• 1.27.37
• 1.27.38
• 1.27.39
• 1.27.40
• 1.27.41
• 1.27.42
• 1.27.43
• 1.27.44
• 1.27.45
• 1.27.46
• 1.27.47
• 1.27.48
• 1.27.49
• 1.27.50
• 1.27.51
• 1.27.52
• 1.27.53
• 1.27.54
• 1.27.55
• 1.27.56
• 1.27.57
• 1.27.58
• 1.27.59
• 1.27.60
• 1.27.61
• 1.27.62
• 1.27.63
• 1.27.64
• 1.27.65
• 1.27.66
• 1.27.67
• 1.27.68
• 1.27.69
• 1.27.70
• 1.27.71
• 1.27.72
• 1.27.73
• 1.27.74
• 1.27.75
• 1.27.76
• 1.27.77
• 1.27.78
• 1.27.79
• 1.27.80

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion