Recent LastFm Tracks Security & Risk Analysis

wordpress.org/plugins/recent-lastfm-tracks

This simple widget includes your LastFm recent tracks into the sidebar.

10 active installs v1.2.3 PHP + WP 3.0+ Updated Jan 5, 2014
lastfmmusicsongtrackswidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Recent LastFm Tracks Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 12yr ago
Risk Assessment

The "recent-lastfm-tracks" v1.2.3 plugin exhibits a mixed security posture. On the positive side, it has a clean vulnerability history with no known CVEs and utilizes prepared statements for all its SQL queries. The absence of known vulnerabilities and the proper handling of database interactions are strong indicators of a well-maintained codebase. However, significant concerns arise from the static analysis. The plugin has zero output escaping applied to its sixteen identified output points, presenting a high risk of Cross-Site Scripting (XSS) vulnerabilities. Furthermore, a taint analysis revealed a flow with an unsanitized path, which, despite not being classified as critical or high severity in this specific scan, indicates a potential avenue for insecure data handling. The lack of nonce checks and capability checks also means that any potential vulnerabilities found within the plugin's functionality could be exploited without proper authorization or verification.

Key Concerns

  • No output escaping
  • Taint flow with unsanitized path
  • No nonce checks
  • No capability checks
Vulnerabilities
None known

Recent LastFm Tracks Security Vulnerabilities

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

Recent LastFm Tracks Code Analysis

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

Output Escaping

0% escaped16 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<recentLastFmTracks> (php\recentLastFmTracks.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Recent LastFm Tracks Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actionwp_headrecent-last-fm-tracks.php:11
actionplugins_loadedrecent-last-fm-tracks.php:107
Maintenance & Trust

Recent LastFm Tracks Maintenance & Trust

Maintenance Signals

WordPress version tested3.7.41
Last updatedJan 5, 2014
PHP min version
Downloads10K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Recent LastFm Tracks Developer Profile

snnooze

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 Recent LastFm Tracks

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/recent-lastfm-tracks/js/jquery.js/wp-content/plugins/recent-lastfm-tracks/js/fm.js
Script Paths
/wp-content/plugins/recent-lastfm-tracks/js/jquery.js/wp-content/plugins/recent-lastfm-tracks/js/fm.js

HTML / DOM Fingerprints

Data Attributes
recentLastFmTracks-WidgetTitlerecentLastFmTracks-usernamerecentLastFmTracks-limitrecentLastFmTracks-cover_sizerecentLastFmTracks-Submit
JS Globals
tumblrScript
FAQ

Frequently Asked Questions about Recent LastFm Tracks