Ice Visual Revisions Security & Risk Analysis

wordpress.org/plugins/ice

Adds revision tracking to the visual editor. Modified, added, or deleted text is shown in color, along with the user and time of change.

10 active installs v1.0-beta2 PHP + WP 3.3+ Updated Unknown
editingnytrevisionstinymcevisual-editor
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Ice Visual Revisions Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "ice" plugin v1.0-beta2 presents a generally positive security posture based on the provided static analysis. There are no identified AJAX handlers, REST API routes, shortcodes, or cron events that act as entry points, significantly minimizing the attack surface. Furthermore, the absence of dangerous functions, raw SQL queries, file operations, and external HTTP requests suggests careful development practices. The presence of capability checks, although only one, is a good sign of access control implementation.

However, the static analysis does reveal some areas for improvement. A concerningly low 17% of total outputs are properly escaped. This could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is directly outputted without adequate sanitization. Additionally, the lack of nonce checks, while not explicitly tied to an attack surface in this limited analysis, is a standard security measure that is missing, which could potentially be exploited in conjunction with other weaknesses.

The vulnerability history is completely clean, with zero known CVEs. This indicates a strong track record and likely suggests that the plugin has not been a target of past exploitation or has been well-maintained. In conclusion, the "ice" plugin has a strong foundation with a small attack surface and good practices regarding SQL and dangerous functions. The primary concern lies with output escaping, and the absence of nonce checks warrants attention to further harden its security.

Key Concerns

  • Low output escaping rate
  • Missing nonce checks
Vulnerabilities
None known

Ice Visual Revisions Security Vulnerabilities

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

Ice Visual Revisions Code Analysis

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

Output Escaping

17% escaped6 total outputs
Attack Surface

Ice Visual Revisions Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
filtermce_external_pluginsice.php:31
filterwp_insert_post_dataice.php:32
filterthe_editor_contentice.php:33
actionwp_headice.php:34
filtermce_buttonsice.php:50
filtermce_buttons_2ice.php:51
filterwp_fullscreen_buttonsice.php:54
filtertiny_mce_before_initice.php:57
actionadmin_print_footer_scriptsice.php:60
Maintenance & Trust

Ice Visual Revisions Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedUnknown
PHP min version
Downloads6K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Ice Visual Revisions Developer Profile

Nikolay Bachiyski

6 plugins · 1K total installs

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

How We Detect Ice Visual Revisions

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/ice/ice/editor_plugin.js/wp-content/plugins/ice/icerevisions/editor_plugin.js/wp-content/plugins/ice/icerevisions/css/ice-revisions.css

HTML / DOM Fingerprints

CSS Classes
ice-wp-insice-wp-del
Data Attributes
data-ciddata-useriddata-usernamedata-time
JS Globals
tinymce
FAQ

Frequently Asked Questions about Ice Visual Revisions