WordPress security by component
Radio Player
Plugin description
Radio Player is a WordPress component with 11 published CVE records in this archive. The latest tracked vulnerability was published Jan 23, 2026; the highest CVE/CNA score is 7.2.
Plugin slug:
radio-playerLatest vulnerability
CVE-2026-24548: Radio Player: Server-side request forgery
Radio Player is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
| Safe version |
|
||
|---|---|---|---|
| Jan 23, 2026 |
CVE-2026-24548
Radio Player: Server-side request forgery
Radio Player is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
|
See mitigation notes |
CVE5.4
NVDPending
|
| Dec 16, 2024 |
CVE-2024-54385
Radio Player: Server-side request forgery
Radio Player is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
|
See mitigation notes |
CVE7.2
NVDPending
|
| Sep 25, 2024 |
CVE-2024-8267
Radio Player – Live Shoutcast, Icecast and Any Audio Stream Player for: Cross-site scripting
Radio Player – Live Shoutcast, Icecast and Any Audio Stream Player for is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVD5.4
|
| Aug 17, 2024 |
CVE-2023-4027
Radio Player: A security weakness
Radio Player is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Aug 17, 2024 |
CVE-2023-4025
Radio Player: A security weakness
Radio Player is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVD5.3
|
| Aug 17, 2024 |
CVE-2023-4024
Radio Player: A security weakness
Radio Player is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVDPending
|
| Jun 11, 2024 |
CVE-2024-34753
Radio Player: A security weakness
Radio Player is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVD5.3
|
| Apr 25, 2024 |
CVE-2024-33592
Radio Player: Server-side request forgery
Radio Player is affected by server-side request forgery. Exposure depends on how the affected operation is made reachable by the site. The vulnerable server can be induced to make attacker-selected network requests.
|
See mitigation notes |
CVE5.4
NVDPending
|
| Apr 17, 2024 |
CVE-2024-32506
Radio Player: A security weakness
Radio Player is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.4
NVDPending
|
| Mar 27, 2024 |
CVE-2024-29811
Radio Player: Cross-site scripting
Radio Player is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVD5.4
|
| Mar 26, 2024 |
CVE-2024-2906
Radio Player: A security weakness
Radio Player is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.5
NVDPending
|