Radio Player Plugin up to 2.0.73 on WordPress Setting authorization

Summaryinfo

A vulnerability identified as problematic has been detected in Radio Player Plugin up to 2.0.73 on WordPress. This impacts an unknown function of the component Setting Handler. Performing a manipulation results in authorization. This vulnerability is cataloged as CVE-2023-4027. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Radio Player Plugin up to 2.0.73 on WordPress. This affects some unknown functionality of the component Setting Handler. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on integrity. The summary by CVE is:

The Radio Player plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update_settings function in versions up to, and including, 2.0.73. This makes it possible for unauthenticated attackers to update plugin settings.

It is possible to read the advisory at wordfence.com. This vulnerability is uniquely identified as CVE-2023-4027 since 07/31/2023. The exploitability is told to be easy. It is possible to initiate the attack remotely. 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/13/2024).

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

Name

• Radio Player Plugin

Version

• 2.0.0
• 2.0.1
• 2.0.2
• 2.0.3
• 2.0.4
• 2.0.5
• 2.0.6
• 2.0.7
• 2.0.8
• 2.0.9
• 2.0.10
• 2.0.11
• 2.0.12
• 2.0.13
• 2.0.14
• 2.0.15
• 2.0.16
• 2.0.17
• 2.0.18
• 2.0.19
• 2.0.20
• 2.0.21
• 2.0.22
• 2.0.23
• 2.0.24
• 2.0.25
• 2.0.26
• 2.0.27
• 2.0.28
• 2.0.29
• 2.0.30
• 2.0.31
• 2.0.32
• 2.0.33
• 2.0.34
• 2.0.35
• 2.0.36
• 2.0.37
• 2.0.38
• 2.0.39
• 2.0.40
• 2.0.41
• 2.0.42
• 2.0.43
• 2.0.44
• 2.0.45
• 2.0.46
• 2.0.47
• 2.0.48
• 2.0.49
• 2.0.50
• 2.0.51
• 2.0.52
• 2.0.53
• 2.0.54
• 2.0.55
• 2.0.56
• 2.0.57
• 2.0.58
• 2.0.59
• 2.0.60
• 2.0.61
• 2.0.62
• 2.0.63
• 2.0.64
• 2.0.65
• 2.0.66
• 2.0.67
• 2.0.68
• 2.0.69
• 2.0.70
• 2.0.71
• 2.0.72
• 2.0.73

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