Post Counter Security & Risk Analysis

wordpress.org/plugins/cybrosys-post-counter

Counting Views, Words and Characters of the Post.

0 active installs v1.0.0 PHP 7.0+ WP 4.7+ Updated Nov 8, 2022
countpostpost-counterpost-counter-pluginview
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Post Counter Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 3yr ago
Risk Assessment

Based on the provided static analysis, "cybrosys-post-counter" v1.0.0 exhibits a strong security posture with no identified vulnerabilities in its attack surface, code signals, or taint analysis. The absence of AJAX handlers, REST API routes, shortcodes, and cron events significantly limits potential entry points for malicious actors. Furthermore, the code demonstrates good practices by properly escaping all outputs, avoiding dangerous functions, and not making external HTTP requests. The SQL queries, while present, show a healthy proportion using prepared statements, and there are no file operations, reducing the risk of file manipulation vulnerabilities.

While the code analysis is reassuring, the complete lack of nonces and capability checks across all entry points, even though the total entry points are zero, could be a concern if the plugin were to be expanded or updated in the future. The absence of any recorded historical vulnerabilities is a positive indicator, suggesting a history of secure development. However, it's important to acknowledge that this is a v1.0.0 release, and a lack of historical data doesn't guarantee future security. The current version appears to be well-secured based on the data, but future development should maintain these standards and address any potential gaps in authentication and authorization checks if new entry points are introduced.

Key Concerns

  • No nonce checks found
  • No capability checks found
Vulnerabilities
None known

Post Counter Security Vulnerabilities

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

Post Counter Code Analysis

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

SQL Query Safety

67% prepared3 total queries

Output Escaping

100% escaped18 total outputs
Attack Surface

Post Counter Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 9
filterthe_contentpost-view.php:19
actionwp_headpost-view.php:20
actionwp_enqueue_scriptspost-view.php:21
filtermanage_posts_columnspost-view.php:22
filtermanage_posts_columnspost-view.php:23
filtermanage_posts_columnspost-view.php:24
actionmanage_posts_custom_columnpost-view.php:25
actionadmin_menupost-view.php:178
actionadmin_initpost-view.php:179
Maintenance & Trust

Post Counter Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedNov 8, 2022
PHP min version7.0
Downloads751

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Post Counter Developer Profile

Cybrosys

2 plugins · 0 total installs

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

How We Detect Post Counter

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/cybrosys-post-counter/css/cpcp-style.css
Version Parameters
cybrosys-post-counter/css/cpcp-style.css?ver=

HTML / DOM Fingerprints

CSS Classes
pcp-viewpcp-text
FAQ

Frequently Asked Questions about Post Counter