TomS Video Player Security & Risk Analysis

wordpress.org/plugins/toms-video-player

Simply protect your videos from being downloaded 'Directly'.

100 active installs v2.1.8 PHP 7.0+ WP 5.8+ Updated Oct 31, 2022
blockplayer-blockvideo-blockvideo-from-url-blockwordpress-video-player-block
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is TomS Video Player Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 3yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the "toms-video-player" plugin v2.1.8 exhibits an exceptionally strong security posture. The absence of any identified attack vectors, such as AJAX handlers, REST API routes, shortcodes, or cron events that are exposed to unauthorized access, is a significant strength. Furthermore, the code demonstrates excellent security practices with the complete absence of dangerous functions, file operations, and external HTTP requests. All SQL queries are properly prepared, and all output is meticulously escaped, indicating a robust defense against common injection and XSS vulnerabilities. The lack of any recorded CVEs, past or present, further reinforces this positive assessment. The plugin's vulnerability history is clean, suggesting a commitment to security or a lack of historically exploitable flaws. The complete absence of any identified taint flows also indicates that the plugin does not appear to handle user-supplied data in a way that could lead to vulnerabilities.

Vulnerabilities
None known

TomS Video Player Security Vulnerabilities

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

TomS Video Player Code Analysis

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

Output Escaping

100% escaped20 total outputs
Attack Surface

TomS Video Player Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
actioninittoms-video-player.php:20
actionenqueue_block_editor_assetstoms-video-player.php:24
Maintenance & Trust

TomS Video Player Maintenance & Trust

Maintenance Signals

WordPress version tested6.1.10
Last updatedOct 31, 2022
PHP min version7.0
Downloads11K

Community Trust

Rating86/100
Number of ratings3
Active installs100
Developer Profile

TomS Video Player Developer Profile

TomS Caprice

7 plugins · 1K total installs

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

How We Detect TomS Video Player

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/toms-video-player/build/index.js/wp-content/plugins/toms-video-player/build/index.css
Script Paths
/wp-content/plugins/toms-video-player/build/index.js
Version Parameters
/wp-content/plugins/toms-video-player/build/index.js?ver=/wp-content/plugins/toms-video-player/build/index.css?ver=

HTML / DOM Fingerprints

CSS Classes
tomsneddontoms-video-player
HTML Comments
<!-- Add TomS Blocks Category to Gutenberg -->
Data Attributes
nodownloadnofullscreennoremoteplayback
JS Globals
FromPHP
Shortcode Output
<div class="tomsneddon"><div class="toms-video-player"
FAQ

Frequently Asked Questions about TomS Video Player