Cirv Pulse Security & Risk Analysis

wordpress.org/plugins/cirv-pulse

Real-time Core Web Vitals monitoring inside WordPress. Track LCP, INP, CLS and get actionable performance recommendations without leaving your dashboa …

0 active installs v1.0.0 PHP 7.4+ WP 5.8+ Updated Unknown
core-web-vitalslighthousepage-speedperformanceseo
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Cirv Pulse Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The "cirv-pulse" plugin v1.0.0 exhibits a strong security posture based on the provided static analysis. It demonstrates excellent adherence to secure coding practices, with a high percentage of SQL queries using prepared statements and nearly all output properly escaped. The absence of dangerous functions, file operations, and critical or high severity taint flows are all positive indicators. Furthermore, the plugin benefits from a minimal attack surface consisting of only one AJAX handler, which impressively has no reported unauthenticated entry points.

The plugin's vulnerability history is also a significant strength, showing zero known CVEs and no previously recorded vulnerabilities of any severity. This suggests a well-developed and thoroughly tested codebase. The presence of nonce and capability checks on its limited entry points further enhances its security. The only minor point of note is a single external HTTP request, which, in isolation, presents a low risk, but any such request always warrants careful monitoring for potential supply chain or external service vulnerabilities.

In conclusion, "cirv-pulse" v1.0.0 appears to be a secure plugin. Its strengths lie in its robust implementation of fundamental security measures like prepared statements and output escaping, a small and well-protected attack surface, and a clean vulnerability history. While the external HTTP request is a point to be aware of, it does not currently pose a significant risk based on the provided data.

Vulnerabilities
None known

Cirv Pulse Security Vulnerabilities

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

Cirv Pulse Code Analysis

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

SQL Query Safety

67% prepared6 total queries

Output Escaping

98% escaped84 total outputs
Data Flows
All sanitized

Data Flow Analysis

2 flows
cirvpulse_render_settings_tab (cirv-pulse.php:516)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Cirv Pulse Attack Surface

Entry Points1
Unprotected0

AJAX Handlers 1

authwp_ajax_cirvpulse_dismiss_ratingcirv-pulse.php:1102
WordPress Hooks 5
actionadmin_menucirv-pulse.php:154
actionadmin_enqueue_scriptscirv-pulse.php:168
actionadmin_noticescirv-pulse.php:1036
actionadmin_noticescirv-pulse.php:1078
actionadmin_enqueue_scriptscirv-pulse.php:1092
Maintenance & Trust

Cirv Pulse Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedUnknown
PHP min version7.4
Downloads283

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Cirv Pulse Developer Profile

cirvgreen

2 plugins · 0 total installs

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

How We Detect Cirv Pulse

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

Asset Fingerprints

HTML / DOM Fingerprints

CSS Classes
cirvpulse-wrapcirvpulse-tabscirvpulse-tabcirvpulse-cardcirvpulse-score-gridcirvpulse-score-cardcirvpulse-score-valuecirvpulse-score-label+21 more
FAQ

Frequently Asked Questions about Cirv Pulse