Plugiva Pulse Security & Risk Analysis

wordpress.org/plugins/plugiva-pulse

Create lightweight feedback forms and quick polls with yes/no, emoji, and text responses inside WordPress.

0 active installs v1.0.0 PHP 7.4+ WP 6.0+ Updated Feb 19, 2026
engagementfeedbackpollquestionnairesurvey
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Plugiva Pulse Safe to Use in 2026?

Generally Safe

Score 100/100

Plugiva Pulse 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 "plugiva-pulse" plugin v1.0.0 demonstrates a generally good security posture with a strong emphasis on output escaping and a lack of critical code signals like dangerous functions or file operations. The static analysis reveals no taint flows with unsanitized paths, suggesting developers are mindful of data handling. Furthermore, the plugin has no recorded vulnerability history, which is a positive indicator of its current security. However, there are notable areas of concern. The presence of two AJAX handlers without authentication checks creates a significant attack vector that could be exploited by unauthenticated users. While there are nonce and capability checks present, they are not applied to all potential entry points, leaving some functionality exposed. The SQL query preparedness is not ideal, with 43% of queries not utilizing prepared statements, which could lead to SQL injection vulnerabilities if user input is not properly sanitized before being passed to these queries. The plugin's attack surface, while small, has a proportionally high number of unprotected entry points. Overall, the plugin has a promising foundation but requires immediate attention to its unauthenticated AJAX handlers and SQL query sanitization to mitigate significant risks.

Key Concerns

  • AJAX handlers without authentication checks
  • SQL queries not using prepared statements
Vulnerabilities
None known

Plugiva Pulse Security Vulnerabilities

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

Plugiva Pulse Code Analysis

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

SQL Query Safety

57% prepared7 total queries

Output Escaping

97% escaped93 total outputs
Data Flows
All sanitized

Data Flow Analysis

3 flows
handle_bulk_delete (admin\class-responses-page.php:137)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
2 unprotected

Plugiva Pulse Attack Surface

Entry Points4
Unprotected2

AJAX Handlers 2

authwp_ajax_ppls_submit_pulseincludes\class-submissions.php:19
noprivwp_ajax_ppls_submit_pulseincludes\class-submissions.php:20

REST API Routes 1

GET/wp-json/plugiva-pulse/v1/pulsesincludes\class-rest.php:29

Shortcodes 1

[ppls_pulse] includes\class-shortcodes.php:16
WordPress Hooks 13
actionadmin_menuadmin\class-menu.php:14
actionadmin_initadmin\class-pulses-page.php:16
actionadmin_noticesadmin\class-pulses-page.php:17
actionadmin_initadmin\class-responses-page.php:19
actionadmin_initadmin\class-responses-page.php:20
actionadmin_noticesadmin\class-responses-page.php:21
actioninitblocks\pulse\index.php:22
actionenqueue_block_editor_assetsblocks\pulse\index.php:24
actionwp_enqueue_scriptsincludes\class-assets.php:19
actionadmin_enqueue_scriptsincludes\class-assets.php:20
actioninitincludes\class-plugin.php:29
actionrest_api_initincludes\class-rest.php:19
actionplugins_loadedplugiva-pulse.php:25
Maintenance & Trust

Plugiva Pulse Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedFeb 19, 2026
PHP min version7.4
Downloads110

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Plugiva Pulse Developer Profile

Amit Biswas

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 Plugiva Pulse

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/plugiva-pulse/assets/js/ppls-frontend.js/wp-content/plugins/plugiva-pulse/assets/css/ppls-frontend.css/wp-content/plugins/plugiva-pulse/assets/js/ppls-admin.js/wp-content/plugins/plugiva-pulse/editor.js
Script Paths
/wp-content/plugins/plugiva-pulse/assets/js/ppls-frontend.js/wp-content/plugins/plugiva-pulse/assets/js/ppls-admin.js/wp-content/plugins/plugiva-pulse/editor.js
Version Parameters
plugiva-pulse/assets/js/ppls-frontend.js?ver=plugiva-pulse/assets/css/ppls-frontend.css?ver=plugiva-pulse/assets/js/ppls-admin.js?ver=plugiva-pulse/editor.js?ver=

HTML / DOM Fingerprints

CSS Classes
ppls-pulseppls-pulse-formppls-pulse-titleppls-submit
HTML Comments
<!-- Honeypot field (bots only) -->
Data Attributes
data-pulse-iddata-pulse
JS Globals
window.PPLS
REST Endpoints
/wp-json/plugiva-pulse/v1/pulses
Shortcode Output
[ppls_pulse
FAQ

Frequently Asked Questions about Plugiva Pulse