PlayMe Security & Risk Analysis

wordpress.org/plugins/playme

Embeddable Song Request Form for Radio Stations

30 active installs v0.2.8 PHP 5.6+ WP 3.2.1+ Updated Jan 6, 2025
musicradiorequestsongstation
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is PlayMe Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "playme" v0.2.8 plugin exhibits a concerning security posture primarily due to its unprotected entry points and the complete absence of prepared statements for its SQL queries. While the plugin doesn't appear to have a history of known vulnerabilities, this could be more a reflection of its limited exposure or detection rather than inherent security. The static analysis reveals a significant attack surface with 4 out of 5 entry points lacking authentication checks. This means that potentially any user, regardless of their role or logged-in status, could trigger these functions, opening the door for various attacks. The critical weakness lies in the 5 SQL queries which are all executed without prepared statements. This makes the plugin highly susceptible to SQL injection vulnerabilities. While the plugin does perform capability checks and has a good output escaping rate, these strengths are overshadowed by the fundamental flaws in handling user input for database operations and the lack of authorization on its AJAX handlers. Therefore, despite a clean vulnerability history, the plugin should be treated with extreme caution and is not recommended for use without significant remediation.

Key Concerns

  • Unprotected AJAX handlers
  • SQL queries without prepared statements
  • No nonce checks on AJAX handlers
Vulnerabilities
None known

PlayMe Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

PlayMe Code Analysis

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

SQL Query Safety

0% prepared5 total queries

Output Escaping

86% escaped7 total outputs
Attack Surface
4 unprotected

PlayMe Attack Surface

Entry Points5
Unprotected4

AJAX Handlers 4

authwp_ajax_playme_submitrequestplayme.php:44
noprivwp_ajax_playme_submitrequestplayme.php:45
authwp_ajax_playme_fetchrequestsplayme.php:47
authwp_ajax_playme_deleterequestplayme.php:48

Shortcodes 1

[playme] playme.php:263
WordPress Hooks 5
actionwp_enqueue_scriptsplayme.php:30
actionadmin_initplayme.php:53
actionwp_enqueue_scriptsplayme.php:55
actionadmin_menuplayme.php:69
filterwoocommerce_prevent_admin_accessplayme.php:415
Maintenance & Trust

PlayMe Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedJan 6, 2025
PHP min version5.6
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs30
Developer Profile

PlayMe Developer Profile

ERA404

5 plugins · 320 total installs

58
trust score
Avg Security Score
70/100
Avg Patch Time
314 days
View full developer profile
Detection Fingerprints

How We Detect PlayMe

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/playme/styles.css/wp-content/plugins/playme/scripts.js
Script Paths
/wp-content/plugins/playme/scripts.js
Version Parameters
playme/scripts.js?ver=1.1

HTML / DOM Fingerprints

CSS Classes
PlayMeAdminPlayMe_submissionsplayme_timerPlayMe_refreshPlayMe_recaptcha
Data Attributes
data-seconds
JS Globals
ajax_objectPlayMe
REST Endpoints
/wp-json/playme/v1/settings/wp-json/playme/v1/requests
FAQ

Frequently Asked Questions about PlayMe