Is Radio Player safe to use?

Laskyr does not give safety verdicts. Radio Player is closed on wordpress.org. Closed on 2026-01-27 (reason given: Guideline Violation). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep Radio Player on the latest version and remove it if you do not use it.

Which versions of Radio Player are vulnerable?

Known issues on record (newest first): Server-side request forgery (SSRF) (2.0.91 and older); Server-side request forgery (SSRF) (2.0.83 and older, fixed in 2.0.85); Stored cross-site scripting (XSS) (2.0.78 and older); Missing authorization check (2.0.73 and older); Missing authorization check (2.0.73 and older, fixed in 2.0.74); Server-side request forgery (SSRF) (2.0.73 and older, fixed in 2.0.74). The full list with sources is on this page.

What should I do if my Radio Player is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update radio-player). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · radio-player · data as of 2026-11-04

Is Radio Player safe? Known vulnerabilities and latest version

Status: Closed 2026-01-27
Known issues on record: 11
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate radio-player && wp plugin delete radio-player

Check your version

Known vulnerabilities

11 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 11 record(s) do not state which versions are affected.

medium 5.4 CVE-2026-24548 · published 2026-01-23

Server-side request forgery (SSRF) in Radio Player (2.0.91 and older)

Affected: 2.0.91 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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

NVD CVE-2026-24548 Patchstack advisory

high 7.2 CVE-2024-54385 · published 2024-12-16

Server-side request forgery (SSRF) in Radio Player (2.0.83 and older)

Affected: 2.0.83 and older
Fixed in: 2.0.85
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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

NVD CVE-2024-54385 Patchstack advisory

medium 5.4 CVE-2024-8267 · published 2024-09-25

Stored cross-site scripting (XSS) in Radio Player (2.0.78 and older)

Affected: 2.0.78 and older
Fixed in: unknown
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The Radio Player – Live Shoutcast, Icecast and Any Audio Stream Player for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'align' attribute within the 'wp:radio-player' Gutenberg block in all versions up to, and including, 2.0.78 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

NVD CVE-2024-8267 Wordfence advisory Code change (fix)wordpress.org Plugin source

medium 5.3 CVE-2023-4024 · published 2024-08-17

Missing authorization check in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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

NVD CVE-2023-4024 Wordfence advisory Code change (fix)plugins.svn.wordpress.org

medium 5.3 CVE-2023-4025 · published 2024-08-17

Missing authorization check in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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

NVD CVE-2023-4025 Wordfence advisory Code change (fix)plugins.svn.wordpress.org

medium 5.3 CVE-2023-4027 · published 2024-08-17

Missing authorization check in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: unknown
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2023-4027 Wordfence advisory Code change (fix)plugins.svn.wordpress.org

medium 5.3 CVE-2024-34753 · published 2024-06-11

Missing authorization check in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: 2.0.74
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Missing Authorization vulnerability in SoftLab Radio Player.This issue affects Radio Player: from n/a through 2.0.73.

NVD CVE-2024-34753 Patchstack advisory

medium 5.4 CVE-2024-33592 · published 2024-04-25

Server-side request forgery (SSRF) in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: 2.0.74
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

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

NVD CVE-2024-33592 Patchstack advisory

medium 5.4 CVE-2024-32506 · published 2024-04-17

Information disclosure in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: 2.0.74
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in SoftLab Radio Player.This issue affects Radio Player: from n/a through 2.0.73.

NVD CVE-2024-32506 Patchstack advisory

medium 5.4 CVE-2024-29811 · published 2024-03-27

Stored cross-site scripting (XSS) in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: 2.0.74
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in SoftLab Radio Player allows Stored XSS.This issue affects Radio Player: from n/a through 2.0.73.

NVD CVE-2024-29811 Patchstack advisory

medium 6.5 CVE-2024-2906 · published 2024-03-26

Missing authorization check in Radio Player (2.0.73 and older)

Affected: 2.0.73 and older
Fixed in: 2.0.74
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in SoftLab Radio Player.This issue affects Radio Player: from n/a through 2.0.73.

NVD CVE-2024-2906 Patchstack advisory

Recent activity

2026-01-27 — closed on wordpress.org (Guideline Violation).
2026-01-23 — Server-side request forgery (SSRF) disclosed (CVE-2026-24548), fix version not stated.
2024-12-16 — Server-side request forgery (SSRF) disclosed (CVE-2024-54385), fixed in 2.0.85.
2024-09-25 — Stored cross-site scripting (XSS) disclosed (CVE-2024-8267), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Radio Player (radio-player) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Missing authorization (5) · Server-side request forgery (SSRF) (3) · Cross-site scripting (XSS) (2) · Sensitive data exposure (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/radio-player (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/radio-player"><img src="https://laskyr.com/plugins/radio-player/badge.svg" alt="Radio Player vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Radio Player safe? Known vulnerabilities and latest version

Radio Player is closed on wordpress.org

What to do

Check your version

Known vulnerabilities

Server-side request forgery (SSRF) in Radio Player (2.0.91 and older)

Server-side request forgery (SSRF) in Radio Player (2.0.83 and older)

Stored cross-site scripting (XSS) in Radio Player (2.0.78 and older)

Missing authorization check in Radio Player (2.0.73 and older)

Missing authorization check in Radio Player (2.0.73 and older)

Missing authorization check in Radio Player (2.0.73 and older)

Missing authorization check in Radio Player (2.0.73 and older)

Server-side request forgery (SSRF) in Radio Player (2.0.73 and older)

Information disclosure in Radio Player (2.0.73 and older)

Stored cross-site scripting (XSS) in Radio Player (2.0.73 and older)

Missing authorization check in Radio Player (2.0.73 and older)

Recent activity

Get an email when Radio Player has a new vulnerability

Browse vulnerabilities

Where this data comes from