Progress Content Security & Risk Analysis

wordpress.org/plugins/progress-content

Add an personalizable progress indicator for your user on all your website.

10 active installs v1.2 PHP 7.2+ WP 5.0+ Updated Sep 15, 2024
progressprogress-barscrollscroll-contenttop-bar
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Progress Content Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

The "progress-content" plugin v1.2 exhibits a strong security posture based on the provided static analysis. The absence of any AJAX handlers, REST API routes, shortcodes, or cron events significantly limits its attack surface, with zero unprotected entry points. The code also demonstrates good practices by exclusively using prepared statements for SQL queries and incorporating nonce checks. However, a concerning area is the output escaping, where 28% of outputs remain unescaped, presenting a potential risk for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is involved in these outputs. The plugin has no recorded vulnerability history, which is a positive indicator, suggesting a history of secure development or infrequent targeting. Despite the lack of critical issues, the unescaped output warrants attention.

Key Concerns

  • Unescaped output (28%)
Vulnerabilities
None known

Progress Content Security Vulnerabilities

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

Progress Content Release Timeline

v1.2Current
v1.1
v1.0
Code Analysis
Analyzed Mar 16, 2026

Progress Content Code Analysis

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

Output Escaping

72% escaped43 total outputs
Data Flows · Security
All sanitized

Data Flow Analysis

2 flows
progcontent_adminPage (progress.class.php:89)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Progress Content Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 6
actionadmin_menuprogress.class.php:7
actionwp_body_openprogress.class.php:8
actionwp_enqueue_scriptsprogress.class.php:9
actionadmin_enqueue_scriptsprogress.class.php:10
actioninitprogress.class.php:11
filterplugin_action_links_progress-content/index.phpprogress.class.php:14
Maintenance & Trust

Progress Content Maintenance & Trust

Maintenance Signals

WordPress version tested6.6.5
Last updatedSep 15, 2024
PHP min version7.2
Downloads829

Community Trust

Rating100/100
Number of ratings2
Active installs10
Developer Profile

Progress Content Developer Profile

Les Vlogs d'un dev

1 plugin · 10 total installs

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

How We Detect Progress Content

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/progress-content/progress.css/wp-content/plugins/progress-content/progress.js/wp-content/plugins/progress-content/pages/progress-admin.css/wp-content/plugins/progress-content/pages/progress-admin.js
Script Paths
progress.jsprogress-admin.js
Version Parameters
progress-content/progress.css?ver=progress-content/progress.js?ver=

HTML / DOM Fingerprints

CSS Classes
progress-style-1progress-style-2
Shortcode Output
<div id="__progress_bar_front"
FAQ

Frequently Asked Questions about Progress Content