TinyMCE Recover Security & Risk Analysis

wordpress.org/plugins/da-tinymce-restore

Restores two buttons removed in TinyMCE with WordPress 4.7: Underline and Justify.

600 active installs v1.2 PHP + WP 4.7+ Updated Jun 15, 2019
4-7justifytinymceunderline
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is TinyMCE Recover Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 6yr ago
Risk Assessment

The da-tinymce-restore plugin version 1.2 presents a generally strong security posture based on the provided static analysis. The absence of any identified attack surface (AJAX handlers, REST API routes, shortcodes, cron events) is a significant positive, as it drastically reduces the potential entry points for attackers. Furthermore, the code analysis reveals commendable security practices, including the complete use of prepared statements for SQL queries, proper output escaping for all outputs, and a lack of dangerous functions, file operations, external HTTP requests, and unhandled nonce or capability checks. The taint analysis also shows no concerning flows with unsanitized paths.

The vulnerability history for this plugin is also completely clean, with no recorded CVEs of any severity. This lack of past vulnerabilities, coupled with the robust static analysis findings, suggests a well-developed and securely coded plugin. However, it's important to note that the analysis indicates 0 nonce checks and 0 capability checks. While this might be acceptable if there are truly no entry points, it represents a potential weakness if the plugin were to evolve and gain entry points without implementing these fundamental security measures. Bundled libraries can also be a concern; in this case, TinyMCE v1.2 is bundled, and while no specific vulnerability is mentioned for this version, keeping bundled libraries up-to-date is a general security best practice.

In conclusion, the da-tinymce-restore v1.2 plugin demonstrates a high level of security due to its minimal attack surface and adherence to secure coding practices like prepared statements and output escaping. The absence of past vulnerabilities further reinforces this positive assessment. The primary area for vigilance is the lack of explicit nonce and capability checks, which, while not an immediate issue given the current analysis, represents a potential blind spot for future development. The bundled TinyMCE library also warrants a minor consideration for potential future updates.

Key Concerns

  • Bundled library TinyMCE v1.2 potentially outdated
  • 0 Nonce checks present
  • 0 Capability checks present
Vulnerabilities
None known

TinyMCE Recover Security Vulnerabilities

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

TinyMCE Recover 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

TinyMCE1.2
Attack Surface

TinyMCE Recover Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 1
filtermce_buttonsda-tinymce-restore.php:15
Maintenance & Trust

TinyMCE Recover Maintenance & Trust

Maintenance Signals

WordPress version tested4.9.29
Last updatedJun 15, 2019
PHP min version
Downloads11K

Community Trust

Rating0/100
Number of ratings0
Active installs600
Developer Profile

TinyMCE Recover Developer Profile

Daniele Alessandra

3 plugins · 1K total installs

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

How We Detect TinyMCE Recover

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about TinyMCE Recover