WP Reading Progress Security & Risk Analysis

wordpress.org/plugins/wp-reading-progress

Light weight fully customizable reading progress bar. Sticks to top, bottom or sticky menu, with fallback for small screens. Includes ert (beta).

3K active installs v1.7.0 PHP 5.6+ WP 4.9+ Updated Feb 11, 2026
estimated-reading-timeprogressprogressbarreading
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Reading Progress Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 1mo ago
Risk Assessment

The wp-reading-progress v1.7.0 plugin exhibits a generally good security posture based on the provided static analysis. The absence of dangerous functions, reliance on prepared statements for all SQL queries, and the presence of nonce and capability checks are positive indicators. Furthermore, the lack of known vulnerabilities and critical taint flows suggests a mature and well-maintained codebase.

However, a concern arises from the output escaping. With 31 total outputs and only 71% properly escaped, this leaves a portion of the plugin's output potentially vulnerable to Cross-Site Scripting (XSS) attacks. While the attack surface is small and currently has no unprotected entry points, this unescaped output represents the most significant risk identified in the code analysis.

In conclusion, the plugin demonstrates strong practices in critical areas like SQL handling and authentication. The primary weakness lies in the insufficient output escaping. The absence of any historical vulnerabilities is a strong positive, suggesting a commitment to security. Addressing the output escaping issue would significantly strengthen its overall security.

Key Concerns

  • Insufficient output escaping (29% unescaped)
Vulnerabilities
None known

WP Reading Progress Security Vulnerabilities

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

WP Reading Progress Code Analysis

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

Output Escaping

71% escaped31 total outputs
Attack Surface

WP Reading Progress Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[wp-reading-progress-ert] wp-reading-progress.php:80
WordPress Hooks 8
actioninitwp-reading-progress.php:22
actionwpwp-reading-progress.php:23
actionadmin_initwp-reading-progress.php:33
actionadmin_menuwp-reading-progress.php:34
actionadd_meta_boxeswp-reading-progress.php:36
actionsave_postwp-reading-progress.php:37
actionwp_headwp-reading-progress.php:71
filterget_the_excerptwp-reading-progress.php:83
Maintenance & Trust

WP Reading Progress Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 11, 2026
PHP min version5.6
Downloads49K

Community Trust

Rating100/100
Number of ratings19
Active installs3K
Developer Profile

WP Reading Progress Developer Profile

Joeri van Veen

6 plugins · 3K total installs

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

How We Detect WP Reading Progress

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/wp-reading-progress/wp-reading-progress.min.js
Script Paths
/wp-content/plugins/wp-reading-progress/admin.min.js/wp-content/plugins/wp-reading-progress/wp-reading-progress.min.js
Version Parameters
wp-reading-progress.min.js?ver=

HTML / DOM Fingerprints

CSS Classes
wp-reading-progress-ert
Data Attributes
data-ertdata-minutes_ruigehond006_show
JS Globals
ruigehond006_c
Shortcode Output
<span class='wp-reading-progress-ert post-
FAQ

Frequently Asked Questions about WP Reading Progress