MEO Wallet Payment Gateway Security & Risk Analysis

wordpress.org/plugins/meo-wallet-wc

MEO Wallet Payment Gateway is a plugin for WooCommerce that provides possibility for merchants to accept payments from Wallet.pt

20 active installs v2.0.2 PHP + WP 4.0+ Updated Oct 9, 2017
gatewaymeo-walletmeowalletpaymentwoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is MEO Wallet Payment Gateway Safe to Use in 2026?

Generally Safe

Score 85/100

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

No known CVEs Updated 8yr ago
Risk Assessment

The meo-wallet-wc plugin v2.0.2 exhibits a generally positive security posture based on the provided static analysis. The plugin demonstrates excellent practices in its handling of SQL queries, exclusively utilizing prepared statements, and the absence of any reported CVEs further reinforces its historical security reliability. The attack surface appears minimal, with no identified AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, no unprotected entry points were found. However, there are areas that warrant attention. The low percentage of properly escaped output (20%) is a significant concern, as it suggests potential for Cross-Site Scripting (XSS) vulnerabilities if user-supplied data is not handled carefully before being displayed to users. Additionally, the lack of nonce checks and capability checks on any identified entry points (though none were found) is a potential weakness if the attack surface were to expand or if the plugin were to introduce such features in the future. The single file operation and external HTTP request, while not inherently problematic, represent potential points of compromise if not secured appropriately.

Key Concerns

  • Low percentage of properly escaped output
  • No nonce checks on entry points
  • No capability checks on entry points
Vulnerabilities
None known

MEO Wallet Payment Gateway Security Vulnerabilities

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

MEO Wallet Payment Gateway Code Analysis

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

Output Escaping

20% escaped20 total outputs
Attack Surface

MEO Wallet Payment Gateway Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 7
actionwoocommerce_api_wc_gateway_meowalletclass\meowallet.class.php:69
filtermultibanco_wallet_email_instructions_table_htmlclass\meowallet.class.php:72
filtermultibanco_wallet_cc_instructions_table_htmlclass\meowallet.class.php:74
filtermeowallet_instructions_payment_receivedclass\meowallet.class.php:76
actionwoocommerce_email_after_order_tableclass\meowallet.class.php:78
actionplugins_loadedinit.php:14
filterwoocommerce_payment_gatewaysinit.php:37
Maintenance & Trust

MEO Wallet Payment Gateway Maintenance & Trust

Maintenance Signals

WordPress version tested4.8.28
Last updatedOct 9, 2017
PHP min version
Downloads3K

Community Trust

Rating0/100
Number of ratings0
Active installs20
Developer Profile

MEO Wallet Payment Gateway Developer Profile

Wipna

3 plugins · 730 total installs

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

How We Detect MEO Wallet 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/meo-wallet-wc/assets/images/mw.png
Version Parameters
meo-wallet-wc/includes/settings-meowallet.php?ver=

HTML / DOM Fingerprints

HTML Comments
<!-- MeoWallet - Email payment received text filter --><!-- Default Variables -->
Data Attributes
data-envdata-apikey
JS Globals
meowallet_wc_params
REST Endpoints
/wc-api/wc_gateway_meowallet
FAQ

Frequently Asked Questions about MEO Wallet Payment Gateway