bbPress Support Forum Checked by Default Security & Risk Analysis

wordpress.org/plugins/bbpress-support-forum-checked-by-default

Checks the "This is a support topic" checkbox by default on bbpress support forums.

10 active installs v1.0 PHP + WP 3.0+ Updated Oct 18, 2013
bbpressbbpress-stay-checkedbbpress-supportbbpress-support-topickeep-check-on-bbpress
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is bbPress Support Forum Checked by Default Safe to Use in 2026?

Generally Safe

Score 85/100

bbPress Support Forum Checked by Default 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 static analysis of bbpress-support-forum-checked-by-default v1.0 reveals a plugin with a minimal attack surface. It has no exposed AJAX handlers, REST API routes, shortcodes, or cron events, which are common entry points for vulnerabilities. The code also demonstrates good practices in using prepared statements for SQL queries and avoiding file operations or external HTTP requests. However, a significant concern is the complete lack of output escaping, with 0% of the 5 identified outputs being properly escaped. This means any data rendered to the user could be manipulated by an attacker, potentially leading to cross-site scripting (XSS) vulnerabilities.

The plugin's vulnerability history is clean, with no known CVEs, which is a positive indicator. This, combined with the limited attack surface, suggests a potentially well-maintained codebase. Nevertheless, the absence of nonce checks and the single capability check without further details about its scope raise questions about authorization. The lack of any taint analysis results is inconclusive but likely due to the lack of observable data flows in the provided analysis.

In conclusion, while the plugin exhibits strengths in its limited attack surface and SQL handling, the critical flaw in output escaping presents a substantial risk. The absence of known vulnerabilities is encouraging, but this does not negate the immediate danger posed by unescaped output. It is recommended that developers prioritize addressing the output escaping issue to mitigate potential XSS attacks.

Key Concerns

  • 0% output escaping
  • Missing nonce checks
Vulnerabilities
None known

bbPress Support Forum Checked by Default Security Vulnerabilities

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

bbPress Support Forum Checked by Default Code Analysis

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

Output Escaping

0% escaped5 total outputs
Attack Surface

bbPress Support Forum Checked by Default Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionbbp_theme_after_topic_form_subscriptionsindex.php:83
actionbbp_theme_after_reply_form_subscriptionindex.php:84
actionadmin_initindex.php:88
actionadmin_menuindex.php:89
Maintenance & Trust

bbPress Support Forum Checked by Default Maintenance & Trust

Maintenance Signals

WordPress version tested3.6.1
Last updatedOct 18, 2013
PHP min version
Downloads3K

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

bbPress Support Forum Checked by Default Developer Profile

The Plugin Factory

5 plugins · 260 total installs

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

How We Detect bbPress Support Forum Checked by Default

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

Asset Fingerprints

HTML / DOM Fingerprints

Data Attributes
bp_bbp_st_is_support
JS Globals
initwindow.onload
FAQ

Frequently Asked Questions about bbPress Support Forum Checked by Default