Payant WooCommerce Payment Gateway Security & Risk Analysis

wordpress.org/plugins/payant-woocommerce

Payant WooCommerce Payment Gateway allows you to accept payments on your WooCommerce store through multiple channels via Payant

10 active installs v2.0 PHP 5.6+ WP 4.7+ Updated Jan 7, 2019
mastercardpayantpayment-gatewaysvisa-cardswoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Payant WooCommerce Payment Gateway Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 7yr ago
Risk Assessment

The 'payant-woocommerce' v2.0 plugin exhibits a mixed security posture. On the positive side, the plugin demonstrates strong practices regarding SQL query sanitization, exclusively using prepared statements, and it has a clean vulnerability history with no recorded CVEs. Furthermore, the static analysis reveals a minimal attack surface, with no identified AJAX handlers, REST API routes, shortcodes, or cron events that could be directly exploited. However, significant concerns arise from the output escaping analysis, where 100% of the identified outputs are not properly escaped. This could lead to cross-site scripting (XSS) vulnerabilities if user-supplied data is directly rendered in the frontend without proper sanitization. The taint analysis also identified flows with unsanitized paths, which, while not classified as critical or high severity in this report, warrants attention as it indicates potential avenues for data manipulation if not handled correctly in conjunction with output mechanisms.

Key Concerns

  • 100% of output escaping is unescaped
  • Unsanitized paths in taint analysis
Vulnerabilities
None known

Payant WooCommerce Payment Gateway Security Vulnerabilities

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

Payant WooCommerce Payment Gateway Code Analysis

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

Output Escaping

0% escaped5 total outputs
Data Flows
3 unsanitized

Data Flow Analysis

3 flows3 with unsanitized paths
payant_woocommerce_init (index.php:13)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Payant WooCommerce Payment Gateway Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionplugins_loadedindex.php:11
actionadmin_noticesindex.php:48
actioninitindex.php:51
filterwoocommerce_payment_gatewaysindex.php:496
Maintenance & Trust

Payant WooCommerce Payment Gateway Maintenance & Trust

Maintenance Signals

WordPress version tested5.0.25
Last updatedJan 7, 2019
PHP min version5.6
Downloads2K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Payant WooCommerce Payment Gateway Developer Profile

PayantNG

1 plugin · 10 total installs

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

How We Detect Payant WooCommerce Payment Gateway

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/payant-woocommerce/assets/images/payant-cards.png

HTML / DOM Fingerprints

CSS Classes
wc-enhanced-select
Data Attributes
data-placeholder
REST Endpoints
/wp-json/wc/v1/payant
FAQ

Frequently Asked Questions about Payant WooCommerce Payment Gateway