BP-TinyMCE Security & Risk Analysis

wordpress.org/plugins/bp-tinymce

Replaces textareas throughout BuddyPress with the TinyMCE rich text box.

10 active installs v0.4.1 PHP + WP + Updated Sep 13, 2011
buddypresseditorrich-texttinymcewysiwyg
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is BP-TinyMCE Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 14yr ago
Risk Assessment

The "bp-tinymce" plugin, version 0.4.1, demonstrates a strong security posture based on the provided static analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the plugin's attack surface. Furthermore, the code analysis indicates excellent security practices, with all SQL queries using prepared statements and all output being properly escaped. There are no identified dangerous functions, file operations, external HTTP requests, or instances of missing nonce or capability checks, which are critical for preventing common WordPress vulnerabilities.

The vulnerability history also paints a positive picture, with no known CVEs recorded for this plugin. This, combined with the clean static analysis results, suggests a well-developed and secure plugin. The bundled TinyMCE library is a common component, but its version is not specified, which could be a minor concern if it's outdated. However, without specific information on its version or known vulnerabilities, this remains a hypothetical risk.

In conclusion, "bp-tinymce" v0.4.1 appears to be a secure plugin with a minimal attack surface and excellent adherence to secure coding practices. The lack of any identified vulnerabilities or high-risk code signals is a significant strength. The only potential, albeit unconfirmed, weakness lies in the possibility of an outdated bundled library, which is not explicitly detailed in the provided data.

Key Concerns

  • Bundled outdated library (TinyMCE)
Vulnerabilities
None known

BP-TinyMCE Security Vulnerabilities

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

BP-TinyMCE Code Analysis

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

Bundled Libraries

TinyMCE
Attack Surface

BP-TinyMCE Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionbp_before_containerbp-tinymce.php:17
actioninitbp-tinymce.php:18
filterbp_forums_allowed_tagsbp-tinymce.php:31
filterbp_activity_allowed_tagsbp-tinymce.php:32
Maintenance & Trust

BP-TinyMCE Maintenance & Trust

Maintenance Signals

WordPress version tested
Last updatedSep 13, 2011
PHP min version
Downloads15K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

BP-TinyMCE Developer Profile

Boone Gorges

27 plugins · 12K total installs

71
trust score
Avg Security Score
88/100
Avg Patch Time
1864 days
View full developer profile
Detection Fingerprints

How We Detect BP-TinyMCE

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/bp-tinymce/bp-tinymce-js.js/wp-content/plugins/bp-tinymce/bp-tinymce-css.css
Script Paths
/wp-content/plugins/bp-tinymce/bp-tinymce-js.js
Version Parameters
bp-tinymce/bp-tinymce-css.css?ver=bp-tinymce/bp-tinymce-js.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about BP-TinyMCE