Debug Bar Query Tracer Security & Risk Analysis

wordpress.org/plugins/debug-bar-query-tracer

A Debug Bar plugin that lets you trace what plugins are causing database queries.

10 active installs v0.1 PHP + WP 3.2+ Updated Unknown
backtracedebug-barperformancewpdb
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Debug Bar Query Tracer Safe to Use in 2026?

Generally Safe

Score 100/100

Debug Bar Query Tracer has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The security posture of the debug-bar-query-tracer plugin v0.1 appears to be quite good based on the provided static analysis. There are no identified attack vectors such as AJAX handlers, REST API routes, or shortcodes exposed to potential attackers. The absence of dangerous functions, file operations, and external HTTP requests further strengthens its security. Importantly, all SQL queries are utilizing prepared statements, mitigating the risk of SQL injection vulnerabilities.

However, a significant concern arises from the output escaping. With 100% of the identified outputs not being properly escaped, this presents a clear risk of Cross-Site Scripting (XSS) vulnerabilities. Any data displayed by the plugin that originates from user input or external sources could potentially be exploited. The plugin also has no recorded vulnerability history, which is positive, but this could also indicate a lack of rigorous security testing or a very small user base.

In conclusion, while the plugin exhibits strong security practices in its input handling and data access layers, the lack of output escaping is a critical flaw that needs immediate attention. The absence of vulnerabilities in its history is a good sign, but it shouldn't overshadow the identified XSS risk. Addressing the output escaping is paramount to improving the plugin's overall security.

Key Concerns

  • Unescaped output detected
Vulnerabilities
None known

Debug Bar Query Tracer Security Vulnerabilities

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

Debug Bar Query Tracer 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

Debug Bar Query Tracer Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 2
filterdebug_bar_panelsgalahad-query-tracer.php:38
filterqueryTracer.php:48
Maintenance & Trust

Debug Bar Query Tracer Maintenance & Trust

Maintenance Signals

WordPress version tested3.2.1
Last updatedUnknown
PHP min version
Downloads5K

Community Trust

Rating20/100
Number of ratings1
Active installs10
Developer Profile

Debug Bar Query Tracer Developer Profile

Chris M.

2 plugins · 60 total installs

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

How We Detect Debug Bar Query Tracer

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/debug-bar-query-tracer/Tracer.php/wp-content/plugins/debug-bar-query-tracer/Panel.php

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Debug Bar Query Tracer