LiquidPoll Plugin up to 3.3.68 on WordPress authorization

Summaryinfo

A vulnerability marked as problematic has been reported in LiquidPoll Plugin up to 3.3.68 on WordPress. This vulnerability affects unknown code. This manipulation causes authorization. This vulnerability appears as CVE-2023-36531. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability was found in LiquidPoll Plugin up to 3.3.68 on WordPress. It has been declared as problematic. Affected by this vulnerability is an unknown code. 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. The summary by CVE is:

Missing Authorization vulnerability in LiquidPoll LiquidPoll – Advanced Polls for Creators and Brands allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects LiquidPoll – Advanced Polls for Creators and Brands: from n/a through 3.3.68.

The weakness was presented by Abdi Pranata. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2023-36531 since 06/22/2023. The exploitation appears to be easy. The attack can be launched remotely. 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 12/13/2024).

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

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• LiquidPoll Plugin

Version

• 3.3.0
• 3.3.1
• 3.3.2
• 3.3.3
• 3.3.4
• 3.3.5
• 3.3.6
• 3.3.7
• 3.3.8
• 3.3.9
• 3.3.10
• 3.3.11
• 3.3.12
• 3.3.13
• 3.3.14
• 3.3.15
• 3.3.16
• 3.3.17
• 3.3.18
• 3.3.19
• 3.3.20
• 3.3.21
• 3.3.22
• 3.3.23
• 3.3.24
• 3.3.25
• 3.3.26
• 3.3.27
• 3.3.28
• 3.3.29
• 3.3.30
• 3.3.31
• 3.3.32
• 3.3.33
• 3.3.34
• 3.3.35
• 3.3.36
• 3.3.37
• 3.3.38
• 3.3.39
• 3.3.40
• 3.3.41
• 3.3.42
• 3.3.43
• 3.3.44
• 3.3.45
• 3.3.46
• 3.3.47
• 3.3.48
• 3.3.49
• 3.3.50
• 3.3.51
• 3.3.52
• 3.3.53
• 3.3.54
• 3.3.55
• 3.3.56
• 3.3.57
• 3.3.58
• 3.3.59
• 3.3.60
• 3.3.61
• 3.3.62
• 3.3.63
• 3.3.64
• 3.3.65
• 3.3.66
• 3.3.67
• 3.3.68

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion