Prince Radio Player Plugin up to 2.0.91 on WordPress server-side request forgery

Summaryinfo

A vulnerability classified as critical has been found in Prince Radio Player Plugin up to 2.0.91 on WordPress. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in server-side request forgery. This vulnerability is known as CVE-2026-24548. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in Prince Radio Player Plugin up to 2.0.91 on WordPress. This affects some unknown processing. 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. The summary by CVE is:

Server-Side Request Forgery (SSRF) vulnerability in Prince Radio Player radio-player allows Server Side Request Forgery.This issue affects Radio Player: from n/a through <= 2.0.91.

The weakness was published by Nabil Irawan. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2026-24548 since 01/23/2026. The exploitability is told to be easy. It is possible to initiate the attack 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 01/23/2026).

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

Vendor

• Prince

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
• 2.0.74
• 2.0.75
• 2.0.76
• 2.0.77
• 2.0.78
• 2.0.79
• 2.0.80
• 2.0.81
• 2.0.82
• 2.0.83
• 2.0.84
• 2.0.85
• 2.0.86
• 2.0.87
• 2.0.88
• 2.0.89
• 2.0.90
• 2.0.91

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