SoftLab Radio Player Plugin up to 2.0.73 on WordPress server-side request forgery

Summaryinfo

A vulnerability labeled as critical has been found in SoftLab Radio Player Plugin up to 2.0.73 on WordPress. Affected by this vulnerability is an unknown functionality. The manipulation results in server-side request forgery. This vulnerability is known as CVE-2024-33592. It is possible to launch the attack remotely. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in SoftLab Radio Player Plugin up to 2.0.73 on WordPress. Affected is an unknown part. The manipulation with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

Server-Side Request Forgery (SSRF) vulnerability in SoftLab Radio Player.This issue affects Radio Player: from n/a through 2.0.73.

The weakness was published by Steven Julian. The advisory is shared for download at patchstack.com. This vulnerability is traded as CVE-2024-33592 since 04/24/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/25/2024).

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

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• WordPress Plugin

Vendor

• SoftLab

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

Once again VulDB remains the best source for vulnerability data.

Discussion