Last.FM Recent Tracks – WordPress Plugin Security & Risk Analysis

wordpress.org/plugins/recent-tracks-lastfm

With this plugin you can add your recent scrobbled tracks on Last.FM to your site.

10 active installs v1.1 PHP + WP 2.0.2+ Updated Dec 17, 2014
last-fmrecent-trackssongs
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Last.FM Recent Tracks – WordPress Plugin Safe to Use in 2026?

Generally Safe

Score 85/100

Last.FM Recent Tracks – WordPress Plugin has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 11yr ago
Risk Assessment

The "recent-tracks-lastfm" v1.1 plugin exhibits a generally low risk profile based on the provided static analysis. It has a very small attack surface, with only one shortcode, and importantly, no identified AJAX handlers or REST API routes that are unprotected. The code also demonstrates good practices regarding SQL queries, with 100% using prepared statements, and no critical or high-severity taint flows were detected.

However, there are significant areas of concern that temper the overall positive assessment. The most glaring issue is that 0% of output is properly escaped, meaning any data rendered by the plugin could be vulnerable to cross-site scripting (XSS) attacks. Furthermore, the plugin lacks any nonce checks or capability checks, which are crucial for verifying user intent and permissions, especially for shortcodes which can be rendered on public-facing pages.

With no recorded vulnerabilities in its history, the plugin appears to have been stable in the past. Nevertheless, the presence of unescaped output and the absence of essential security checks represent tangible, exploitable risks that could be leveraged by attackers. While the plugin has strengths in its limited attack surface and secure SQL practices, the critical lack of output escaping and authorization controls warrants caution.

Key Concerns

  • 0% output escaping
  • 0 nonce checks
  • 0 capability checks
Vulnerabilities
None known

Last.FM Recent Tracks – WordPress Plugin Security Vulnerabilities

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

Last.FM Recent Tracks – WordPress Plugin Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

Last.FM Recent Tracks – WordPress Plugin Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[lastfm] lastfm-recenttracks.php:22
WordPress Hooks 2
actionwp_enqueue_scriptslastfm-recenttracks.php:63
actionadmin_menulastfm-recenttracks.php:69
Maintenance & Trust

Last.FM Recent Tracks – WordPress Plugin Maintenance & Trust

Maintenance Signals

WordPress version tested4.1.42
Last updatedDec 17, 2014
PHP min version
Downloads2K

Community Trust

Rating40/100
Number of ratings1
Active installs10
Developer Profile

Last.FM Recent Tracks – WordPress Plugin Developer Profile

maksimdegtyarev

1 plugin · 10 total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Last.FM Recent Tracks – WordPress Plugin

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/recent-tracks-lastfm/lastfm-style.css

HTML / DOM Fingerprints

CSS Classes
recent-trackstrack-itemtrack-albumtrack-artisttrack-nametrack-description
Shortcode Output
<ul class="recent-tracks"><li class="track-item"><a href="<img src="
FAQ

Frequently Asked Questions about Last.FM Recent Tracks – WordPress Plugin