Radio Tools Security & Risk Analysis

wordpress.org/plugins/radio-tools

Easily add a streaming audio player to your site with a shortcode. Easy to customise!

60 active installs v1.03 PHP + WP 4.0+ Updated Aug 14, 2020
audiomp3radiostreaming-audiovoscast
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Radio Tools Safe to Use in 2026?

Generally Safe

Score 85/100

Radio Tools has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5yr ago
Risk Assessment

The "radio-tools" v1.03 plugin demonstrates a generally positive security posture based on the static analysis. The absence of known CVEs and a clean vulnerability history are significant strengths, suggesting a well-maintained and secure codebase. The plugin also avoids dangerous functions and file operations, and all SQL queries are properly prepared, which are excellent security practices.

However, there are areas for improvement. The plugin exhibits a concerning lack of authorization checks on its entry points. While the current attack surface is small, the complete absence of capability checks and nonce checks on the single shortcode presents a potential risk. This means that any authenticated user, regardless of their role, could potentially trigger the functionality associated with this shortcode. Furthermore, the fact that only 55% of outputs are properly escaped indicates a risk of cross-site scripting (XSS) vulnerabilities if user-supplied data is used in unescaped contexts.

In conclusion, while "radio-tools" v1.03 benefits from a clean vulnerability history and good practices in areas like SQL and dangerous functions, the lack of robust authorization on its entry points and the presence of unescaped output are significant security concerns that warrant attention. Addressing these weaknesses would greatly improve the plugin's overall security.

Key Concerns

  • No capability checks on entry points
  • No nonce checks on entry points
  • Significant portion of output unescaped
Vulnerabilities
None known

Radio Tools Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

Radio Tools Release Timeline

No version history available.
Code Analysis
Analyzed Apr 16, 2026

Radio Tools Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
10
12 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
1
Bundled Libraries
0

Output Escaping

55% escaped22 total outputs
Attack Surface

Radio Tools Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[radio_tools] classes/radio_tools.php:31
WordPress Hooks 7
actiongenerate_rewrite_rulesclasses/radio_tools.php:23
filterquery_varsclasses/radio_tools.php:24
actionparse_requestclasses/radio_tools.php:25
actioninitclasses/radio_tools.php:26
actionwp_enqueue_scriptsclasses/radio_tools.php:27
actionadmin_menuclasses/radio_tools_options.php:25
actionadmin_initclasses/radio_tools_options.php:26
Maintenance & Trust

Radio Tools Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedAug 14, 2020
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs60
Developer Profile

Radio Tools Developer Profile

UIUX Lab

16 plugins · 800 total installs

79
trust score
Avg Security Score
87/100
Avg Patch Time
32 days
View full developer profile
Detection Fingerprints

How We Detect Radio Tools

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/radio-tools/js/howler.min.js
Script Paths
/wp-content/plugins/radio-tools/js/howler.min.js

HTML / DOM Fingerprints

JS Globals
RADIO_TOOLS_PLUGIN_ASSETSRADIO_TOOLS_PLUGIN_TEMPLATES_PATH
Shortcode Output
[radio_tools]
FAQ

Frequently Asked Questions about Radio Tools