BugPost Security & Risk Analysis

wordpress.org/plugins/bugpost

Simple frontend bug reporting overlay for WordPress. Visitors submit reports with auto-captured browser context and console errors.

0 active installs v1.2.3 PHP 7.4+ WP 5.8+ Updated Apr 15, 2026
bug-reportbug-trackingerror-reportingfeedbackqa
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BugPost Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The "bugpost" plugin v1.2.3 demonstrates a generally strong security posture based on the provided static analysis. The absence of known CVEs and a clean vulnerability history are significant positive indicators. The code also shows excellent adherence to secure coding practices, with 100% of SQL queries using prepared statements and an impressive 99% of outputs being properly escaped. Nonce and capability checks are present on entry points, further strengthening its defenses.

However, a single unsanitized path flow identified during taint analysis, despite being flagged with no critical or high severity, warrants attention. While the attack surface is small and currently protected, this unsanitized path represents a potential vector for attack if not fully understood and mitigated. The presence of file operations without further context could also be a minor concern if they interact with user-supplied data without proper validation.

Overall, "bugpost" appears to be a well-developed and relatively secure plugin. The primary area for review is the identified unsanitized path flow to ensure it does not present a latent vulnerability. The plugin's track record and adherence to core WordPress security best practices are commendable strengths.

Key Concerns

  • Flows with unsanitized paths
Vulnerabilities
None known

BugPost Security Vulnerabilities

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

BugPost Release Timeline

v1.2.3Current
v1.2.2
Code Analysis
Analyzed Apr 16, 2026

BugPost Code Analysis

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

SQL Query Safety

100% prepared6 total queries

Output Escaping

99% escaped167 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

2 flows1 with unsanitized paths
admin_filters (includes/class-bugpost-cpt.php:348)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

BugPost Attack Surface

Entry Points2
Unprotected0

AJAX Handlers 2

authwp_ajax_bugpost_submitincludes/class-bugpost-ajax.php:24
noprivwp_ajax_bugpost_submitincludes/class-bugpost-ajax.php:25
WordPress Hooks 17
actioninitbugpost.php:136
actionadmin_menuincludes/class-bugpost-admin.php:18
actionadmin_initincludes/class-bugpost-admin.php:19
actionadmin_initincludes/class-bugpost-admin.php:20
actionadmin_enqueue_scriptsincludes/class-bugpost-admin.php:21
filterparent_fileincludes/class-bugpost-admin.php:22
filtersubmenu_fileincludes/class-bugpost-admin.php:23
actionadd_meta_boxesincludes/class-bugpost-cpt.php:34
actionsave_post_bugpost_reportincludes/class-bugpost-cpt.php:35
filtermanage_bugpost_report_posts_columnsincludes/class-bugpost-cpt.php:36
actionmanage_bugpost_report_posts_custom_columnincludes/class-bugpost-cpt.php:37
filtermanage_edit-bugpost_report_sortable_columnsincludes/class-bugpost-cpt.php:38
actionpre_get_postsincludes/class-bugpost-cpt.php:39
actionrestrict_manage_postsincludes/class-bugpost-cpt.php:40
actionpre_get_postsincludes/class-bugpost-cpt.php:41
actionwp_enqueue_scriptsincludes/class-bugpost-widget.php:21
actionwp_footerincludes/class-bugpost-widget.php:22
Maintenance & Trust

BugPost Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedApr 15, 2026
PHP min version7.4
Downloads70

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

BugPost Developer Profile

wikifleeksmedia

1 plugin · 0 total installs

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

How We Detect BugPost

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bugpost/assets/css/bugpost-admin.css/wp-content/plugins/bugpost/assets/js/bugpost-admin.js/wp-content/plugins/bugpost/assets/js/bugpost-frontend.js/wp-content/plugins/bugpost/assets/css/bugpost-frontend.css/wp-content/plugins/bugpost/assets/js/bugpost-captcha.js
Version Parameters
bugpost/assets/css/bugpost-admin.css?ver=bugpost/assets/js/bugpost-admin.js?ver=bugpost/assets/js/bugpost-frontend.js?ver=bugpost/assets/css/bugpost-frontend.css?ver=bugpost/assets/js/bugpost-captcha.js?ver=

HTML / DOM Fingerprints

CSS Classes
bugpost-admin-wrapbugpost-feedback-form-wrapperbugpost-feedback-button
Data Attributes
data-bugpost-ajax-urldata-bugpost-nonce
JS Globals
bugpost_admin_params
REST Endpoints
/wp-json/bugpost/v1/submit
FAQ

Frequently Asked Questions about BugPost