Image Counter Security & Risk Analysis

wordpress.org/plugins/image-counter

This plugin adds a small counter to each image in your posts.

10 active installs v0.4.1 PHP + WP 2.8+ Updated Jun 24, 2013
countcounterimageimagesphoto
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Image Counter Safe to Use in 2026?

Generally Safe

Score 85/100

Image Counter 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 "image-counter" plugin v0.4.1 exhibits a strong initial security posture, with no recorded vulnerabilities in its history and a clean static analysis report regarding dangerous functions, SQL queries, file operations, and external HTTP requests. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits the plugin's attack surface, and the limited code signals indicate careful development. However, a critical concern arises from the output escaping: 100% of the five identified output points are not properly escaped. This indicates a potential for Cross-Site Scripting (XSS) vulnerabilities, where malicious scripts could be injected and executed within the WordPress admin or frontend if user-supplied data is not sanitized before being displayed.

The plugin's vulnerability history is a significant strength, showing no known CVEs. This suggests a track record of secure development or a lack of targeted attacks. The sole capability check is a positive sign, indicating an attempt to enforce access control. Despite the lack of identified taint flows or critical security issues in the static analysis, the unescaped output is a serious oversight that could lead to exploitable vulnerabilities. Therefore, while the plugin has a good foundation, the lack of output escaping presents a notable risk.

Key Concerns

  • All identified outputs are unescaped
Vulnerabilities
None known

Image Counter Security Vulnerabilities

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

Image Counter 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
Data Flows
All sanitized

Data Flow Analysis

1 flows
<image-counter-admin> (image-counter-admin.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Image Counter Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 3
actionwp_print_stylesimage-counter.php:34
actionadmin_menuimage-counter.php:124
filterthe_contentimage-counter.php:125
Maintenance & Trust

Image Counter Maintenance & Trust

Maintenance Signals

WordPress version tested3.5.2
Last updatedJun 24, 2013
PHP min version
Downloads4K

Community Trust

Rating20/100
Number of ratings1
Active installs10
Developer Profile

Image Counter Developer Profile

ajayver

5 plugins · 150 total installs

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

How We Detect Image Counter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/image-counter/style.css

HTML / DOM Fingerprints

CSS Classes
imageimage-count
Data Attributes
data-image-counter-options
FAQ

Frequently Asked Questions about Image Counter