Classic Image Button Security & Risk Analysis

wordpress.org/plugins/classic-image-button

Restore the classic image button in the post and page text editor editor of WordPress

20 active installs v1.0.2 PHP + WP 2.6.0+ Updated Mar 24, 2013
borderbuttonbuttonsimageinline
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Classic Image Button Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 13yr ago
Risk Assessment

The "classic-image-button" v1.0.2 plugin exhibits a mixed security posture. On the positive side, the plugin has no recorded vulnerabilities (CVEs) and demonstrates good practices by using prepared statements for all its SQL queries and performing no external HTTP requests or file operations. The lack of cron events and shortcodes also contributes to a reduced attack surface.

However, significant concerns arise from the static code analysis. A notable weakness is the complete absence of output escaping for all identified output points (2 total). This means that any dynamic content rendered by the plugin is susceptible to cross-site scripting (XSS) vulnerabilities, especially if user-supplied data is involved. Furthermore, the taint analysis revealed two flows with unsanitized paths, which, while not classified as critical or high severity in this report, indicate potential for security issues if these paths can be manipulated by an attacker. The absence of nonce and capability checks also means that if any entry points were to be discovered, they would likely be unprotected.

Key Concerns

  • Unescaped output for all identified outputs
  • Taint analysis shows unsanitized paths
  • No nonce checks present
  • No capability checks present
Vulnerabilities
None known

Classic Image Button Security Vulnerabilities

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

Classic Image Button 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
Data Flows
2 unsanitized

Data Flow Analysis

2 flows2 with unsanitized paths
classic_image_button_admin_page (classic_image_button.php:27)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Classic Image Button Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 5
actionadmin_menuclassic_image_button.php:148
filterteeny_mce_buttonsclassic_image_button.php:150
filtermce_buttonsclassic_image_button.php:151
filterteeny_mce_before_initclassic_image_button.php:152
filtertiny_mce_before_initclassic_image_button.php:153
Maintenance & Trust

Classic Image Button Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedMar 24, 2013
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings1
Active installs20
Developer Profile

Classic Image Button Developer Profile

Angelo Mandato

7 plugins · 10K total installs

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

How We Detect Classic Image Button

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
classic_image_button_settings
Data Attributes
name="Settings[disable_inline_styling]"
FAQ

Frequently Asked Questions about Classic Image Button