Dropp Pay Per Use Security & Risk Analysis

wordpress.org/plugins/dropp-pay-per-use

Effortlessly monetize your publication with Dropp Pay Per Use. Accept micropayments for your content.

10 active installs v1.2.0 PHP 7.2+ WP 5.8+ Updated May 9, 2025
micropaymentpay-per-usepaywallpublicationsubscription
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Download
Safety Verdict

Is Dropp Pay Per Use Safe to Use in 2026?

Generally Safe

Score 100/100

Dropp Pay Per Use has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 10mo ago
Risk Assessment

The "dropp-pay-per-use" v1.2.0 plugin exhibits a mixed security posture. While the plugin demonstrates good practices in SQL query preparation and output escaping, with 80% and 90% respectively, there are significant concerns regarding its attack surface. A substantial portion of the plugin's entry points, specifically 9 out of 13, are unprotected by authentication checks. Furthermore, the taint analysis reveals 7 flows with unsanitized paths, with 5 classified as high severity, indicating a potential for malicious data to be processed without proper validation. The absence of any recorded historical vulnerabilities is a positive sign, suggesting that the developers may have a generally cautious approach to security. However, this historical data is limited and doesn't negate the immediate risks identified in the static analysis, particularly the numerous unprotected AJAX handlers and the high-severity taint flows, which represent tangible security weaknesses that should be addressed.

Key Concerns

  • Unprotected AJAX handlers
  • High severity taint flows
  • Unsanitized paths in taint analysis
Vulnerabilities
None known

Dropp Pay Per Use Security Vulnerabilities

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

Dropp Pay Per Use Code Analysis

Dangerous Functions
0
Raw SQL Queries
11
44 prepared
Unescaped Output
32
275 escaped
Nonce Checks
6
Capability Checks
1
File Operations
6
External Requests
1
Bundled Libraries
0

SQL Query Safety

80% prepared55 total queries

Output Escaping

90% escaped307 total outputs
Data Flows
7 unsanitized

Data Flow Analysis

8 flows7 with unsanitized paths
process_signed_payment (includes\class-droppcc-paywall-payment-processor.php:234)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
9 unprotected

Dropp Pay Per Use Attack Surface

Entry Points13
Unprotected9

AJAX Handlers 9

authwp_ajax_dropcc_paywall_add_new_restrictionsincludes\class-droppcc-paywall-admin-ajax.php:21
authwp_ajax_dropcc_paywall_update_restrictionsincludes\class-droppcc-paywall-admin-ajax.php:22
authwp_ajax_dropcc_paywall_fetch_taxonomy_listincludes\class-droppcc-paywall-admin-ajax.php:23
authwp_ajax_dropcc_paywall_delete_planincludes\class-droppcc-paywall-admin-ajax.php:24
authwp_ajax_dropcc_paywall_enable_disabled_planincludes\class-droppcc-paywall-admin-ajax.php:25
authwp_ajax_dropcc_paywall_create_pagesincludes\class-droppcc-paywall-admin-ajax.php:27
authwp_ajax_dropcc_paywall_create_sample_plansincludes\class-droppcc-paywall-admin-ajax.php:28
authwp_ajax_dropcc_paywall_set_cookieincludes\class-droppcc-paywall-frontend-ajax.php:21
noprivwp_ajax_dropcc_paywall_set_cookieincludes\class-droppcc-paywall-frontend-ajax.php:22

Shortcodes 4

[dropp_ref] includes\class-droppcc-paywall-frontend.php:20
[dropp_url] includes\class-droppcc-paywall-frontend.php:21
[dropp_expiry] includes\class-droppcc-paywall-frontend.php:22
[dropp_my_subscriptions] includes\class-droppcc-paywall-frontend.php:23
WordPress Hooks 19
actioninitdropp-pay-per-use.php:215
actionwp_enqueue_scriptsincludes\class-droppcc-paywall-frontend.php:25
actionwp_headincludes\class-droppcc-paywall-frontend.php:27
actionadmin_initincludes\class-droppcc-paywall-log.php:20
actioninitincludes\class-droppcc-paywall-log.php:21
actiondropp_paywall_data_log_cronincludes\class-droppcc-paywall-log.php:22
actionadd_meta_boxesincludes\class-droppcc-paywall-metabox.php:20
actionsave_postincludes\class-droppcc-paywall-metabox.php:21
actiontemplate_redirectincludes\class-droppcc-paywall-payment-processor.php:44
actionwpincludes\class-droppcc-paywall-restrict-content.php:26
filterthe_excerptincludes\class-droppcc-paywall-restrict-content.php:36
filterget_the_excerptincludes\class-droppcc-paywall-restrict-content.php:38
filterthe_contentincludes\class-droppcc-paywall-restrict-content.php:43
filterthe_contentincludes\class-droppcc-paywall-restrict-content.php:46
actionadmin_menuincludes\class-droppcc-paywall-settings-page.php:21
actionadmin_initincludes\class-droppcc-paywall-settings-page.php:22
actionadmin_enqueue_scriptsincludes\class-droppcc-paywall-settings-page.php:23
actionadmin_noticesincludes\class-droppcc-paywall-settings-page.php:24
actionadmin_initincludes\class-droppcc-paywall-subscribers.php:20

Scheduled Events 1

dropp_paywall_data_log_cron
Maintenance & Trust

Dropp Pay Per Use Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedMay 9, 2025
PHP min version7.2
Downloads2K

Community Trust

Rating100/100
Number of ratings1
Active installs10
Developer Profile

Dropp Pay Per Use Developer Profile

Dropp Payment App

4 plugins · 20 total installs

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

How We Detect Dropp Pay Per Use

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/dropp-pay-per-use/build/index.js/wp-content/plugins/dropp-pay-per-use/build/index.asset.php
Script Paths
/wp-content/plugins/dropp-pay-per-use/build/index.js

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Dropp Pay Per Use