Tampile temperature converter Security & Risk Analysis

wordpress.org/plugins/tampile-temperature-conversion-widget

Easy widget for wordpress to provide your users the facility to convert temperature: fahrenheit, celsius, kelvin, rankine.

10 active installs v1.2.2 PHP + WP 2.0.2+ Updated Jun 30, 2021
celsiusfahrenheitrankintemperature-conversionwidget
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Tampile temperature converter Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 4yr ago
Risk Assessment

The "tampile-temperature-conversion-widget" v1.2.2 plugin exhibits a generally strong security posture based on the provided static analysis. The absence of any identified AJAX handlers, REST API routes, shortcodes, or cron events with exposed entry points suggests a minimal attack surface. Furthermore, the lack of dangerous functions, file operations, external HTTP requests, and the use of prepared statements for all SQL queries are positive indicators of secure coding practices. The plugin also has no recorded vulnerability history, which is a significant strength. However, a notable concern is the complete lack of output escaping for the two identified output instances. This could potentially lead to cross-site scripting (XSS) vulnerabilities if the data being output is not inherently sanitized by the source. The absence of nonce checks and capability checks also indicates a potential weakness, as these are standard security measures for protecting against unauthorized actions and privilege escalation, particularly if any of the identified output mechanisms were to become interactive or exposed to external input in the future. Despite the lack of identified vulnerabilities and a clean history, the unescaped output and missing checks warrant attention.

Key Concerns

  • 0% output escaping for identified outputs
  • 0 Nonce checks present
  • 0 Capability checks present
Vulnerabilities
None known

Tampile temperature converter Security Vulnerabilities

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

Tampile temperature converter Release Timeline

v1.2.2Current
v1.2.1
v1.2
v1.1
v1.0
Code Analysis
Analyzed Apr 16, 2026

Tampile temperature converter Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

Tampile temperature converter Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
actionplugins_loadedtampile.php:102
Maintenance & Trust

Tampile temperature converter Maintenance & Trust

Maintenance Signals

WordPress version tested5.7.15
Last updatedJun 30, 2021
PHP min version
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Tampile temperature converter Developer Profile

Lucian Apostol

9 plugins · 3K total installs

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

How We Detect Tampile temperature converter

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
id="tampileform"name="tampile_from"id="tampile_from"name="tampile_to"id="tampile_to"name="tampile_value"+3 more
JS Globals
tampile_calculator
Shortcode Output
<form id="tampileform" onsubmit="return tampile_calculator(this);" method="post"><input type="text" name="tampile_value" id="tampile_value" size="9"; /><input type="text" name="tampile_result" id="tampile_result" size="9"; /><select name="tampile_from" id="tampile_from">
FAQ

Frequently Asked Questions about Tampile temperature converter