IntaSend Payment Security & Risk Analysis

wordpress.org/plugins/intasend-payment

Securely collect M-Pesa and card payments (Visa and Mastercard) (WooCommerce Plugin).

400 active installs v1.0.20 PHP 7.4+ WP 6.0+ Updated Aug 27, 2025
checkoutm-pesamastercardpaymentsvisa
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is IntaSend Payment Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 8mo ago
Risk Assessment

The "intasend-payment" plugin v1.0.20 exhibits a generally good security posture based on the static analysis. The absence of known CVEs and any recorded historical vulnerabilities is a significant strength, suggesting a developer who is either vigilant about security or has not yet had vulnerabilities discovered. The code signals also indicate positive practices, with 100% of SQL queries using prepared statements and a high percentage (83%) of output being properly escaped. The limited attack surface, with zero entry points identified for AJAX, REST API, shortcodes, and cron events, further contributes to its secure profile.

However, there are areas that warrant attention. The most notable concern is the complete lack of nonce checks and capability checks. This is a significant weakness, as it means that any unauthenticated or low-privileged user could potentially interact with functions that were not designed for them. While the static analysis shows zero unprotected entry points in terms of direct authentication checks, the absence of capability checks on any potential (though currently zero) internal functions leaves room for privilege escalation or unauthorized actions if new entry points were introduced or if existing ones have implicit access. The file operations and external HTTP requests, while not inherently risky, should be monitored for potential abuses if the input feeding them is not sufficiently sanitized, although the taint analysis did not reveal any unsanitized paths in the analyzed flows.

In conclusion, while the plugin benefits from a clean vulnerability history and good SQL and output sanitization, the lack of nonce and capability checks represents a critical oversight. This weakness could be exploited if any functionality, even if currently inaccessible, were to be triggered in an unintended context. The developer should prioritize implementing robust nonce and capability checks to fully secure the plugin against potential authorization bypasses and privilege escalation attacks.

Key Concerns

  • Missing nonce checks
  • Missing capability checks
  • File operations detected
  • External HTTP requests detected
  • Some outputs not properly escaped
Vulnerabilities
None known

IntaSend Payment Security Vulnerabilities

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

IntaSend Payment Release Timeline

v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
Code Analysis
Analyzed Mar 16, 2026

IntaSend Payment Code Analysis

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

Output Escaping

83% escaped29 total outputs
Attack Surface

IntaSend Payment Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
filterwoocommerce_payment_gatewaysintasend-gateway.php:22
actionbefore_woocommerce_initintasend-gateway.php:30
actionplugins_loadedintasend-gateway.php:41
actionwoocommerce_blocks_loadedintasend-gateway.php:42
actionwoocommerce_blocks_payment_method_type_registrationintasend-gateway.php:51
actionwoocommerce_api_intasend_webhookintasend-gateway.php:94
actionwp_enqueue_scriptsintasend-gateway.php:96
Maintenance & Trust

IntaSend Payment Maintenance & Trust

Maintenance Signals

WordPress version tested6.8.5
Last updatedAug 27, 2025
PHP min version7.4
Downloads14K

Community Trust

Rating100/100
Number of ratings1
Active installs400
Developer Profile

IntaSend Payment Developer Profile

Felix Cheruiyot

2 plugins · 460 total installs

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

How We Detect IntaSend Payment

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/intasend-payment/assets/js/intasend-inline-min.js
Script Paths
/wp-content/plugins/intasend-payment/assets/js/intasend-inline-min.js
Version Parameters
intasend-payment/assets/js/intasend-inline-min.js?ver=

HTML / DOM Fingerprints

JS Globals
window.wc_checkout_params
REST Endpoints
/wp-json/wc/v3/orders/
FAQ

Frequently Asked Questions about IntaSend Payment