MC Annual Upcounter Security & Risk Analysis

wordpress.org/plugins/mc-annual-upcounter

Pounds of wasted food, gallons of ice cream, babies born, cars sold ... any number that accrues througout the year, updated live on the website page.

10 active installs v2.1.2 PHP 7.0+ WP 4.7+ Updated Nov 25, 2025
annual-countercount-by-daylive-counterup-counteryearly-total
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MC Annual Upcounter Safe to Use in 2026?

Generally Safe

Score 100/100

MC Annual Upcounter has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5mo ago
Risk Assessment

The "mc-annual-upcounter" v2.1.2 plugin exhibits a generally strong security posture with no known vulnerabilities or CVEs recorded, which is a significant positive indicator. The static analysis reveals a minimal attack surface, with only one shortcode and no AJAX handlers or REST API routes exposed without authentication. Furthermore, the code demonstrates good practices by using prepared statements for all SQL queries and performing no file operations or external HTTP requests. However, a notable concern is the low percentage of properly escaped output, with only one-third of identified outputs being sanitized. This could potentially lead to cross-site scripting (XSS) vulnerabilities if user-controlled data is present in the unescaped outputs. The absence of any identified taint flows is a positive sign, suggesting that sensitive data is not being mishandled. Overall, while the plugin avoids common pitfalls like raw SQL or unauthenticated entry points, the unescaped output represents a tangible risk that needs attention. The lack of vulnerability history is encouraging but doesn't negate the findings from the static analysis.

Key Concerns

  • Low output escaping percentage
Vulnerabilities
None known

MC Annual Upcounter Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Version History

MC Annual Upcounter Release Timeline

No version history available.
Code Analysis
Analyzed Mar 16, 2026

MC Annual Upcounter Code Analysis

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

Output Escaping

33% escaped6 total outputs
Attack Surface

MC Annual Upcounter Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[mcau_annual_upcounter] inc\mc6397au_shortcode.php:18
WordPress Hooks 3
actionwp_headmc-annual-upcounter.php:35
actionadmin_menumc-annual-upcounter.php:162
actionadmin_initmc-annual-upcounter.php:163
Maintenance & Trust

MC Annual Upcounter Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedNov 25, 2025
PHP min version7.0
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

MC Annual Upcounter Developer Profile

Mike Hickcox

6 plugins · 240 total installs

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

How We Detect MC Annual Upcounter

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

Asset Fingerprints

Script Paths
/wp-content/plugins/mc-annual-upcounter/assets/MC-AU-Head.jpg

HTML / DOM Fingerprints

Data Attributes
id="mc6397au_Counter"
JS Globals
incrementfrequency
Shortcode Output
<span id='mc6397au_Counter'>Calculating ...</span>
FAQ

Frequently Asked Questions about MC Annual Upcounter