Claudio Sanches – PagSeguro for WooCommerce Security & Risk Analysis

wordpress.org/plugins/woocommerce-pagseguro

Adds PagSeguro gateway to the WooCommerce plugin

10K active installs v2.14.0 PHP + WP 4.0+ Updated Aug 10, 2020
pagseguropaymentwoocommerce
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Claudio Sanches – PagSeguro for WooCommerce Safe to Use in 2026?

Generally Safe

Score 85/100

Claudio Sanches – PagSeguro for WooCommerce has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 5yr ago
Risk Assessment

The WooCommerce PagSeguro plugin v2.14.0 demonstrates a strong security posture based on the provided static analysis. The plugin exhibits good practices with no identified dangerous functions, all SQL queries utilizing prepared statements, and a high percentage of properly escaped output. The attack surface is minimal, with no AJAX handlers, REST API routes, shortcodes, or cron events, and importantly, all identified entry points appear to be protected.

Taint analysis reveals no critical or high severity flows, and there is no known vulnerability history for this plugin, including no unpatched CVEs. This suggests a well-maintained and secure codebase that has not been associated with known security issues. The presence of capability checks indicates an effort to enforce user permissions. The only minor concern is the single external HTTP request, which, while not inherently a vulnerability, warrants attention for potential issues like insecure transport or unintended data exposure if not handled carefully.

Overall, this plugin appears to be very secure. The lack of vulnerabilities, robust coding practices, and minimal attack surface are significant strengths. The absence of critical flaws in taint analysis and the clean vulnerability history are particularly reassuring. The single external HTTP request is a minor point of consideration rather than a direct risk based on the provided data.

Key Concerns

  • External HTTP requests present
Vulnerabilities
None known

Claudio Sanches – PagSeguro for WooCommerce Security Vulnerabilities

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

Claudio Sanches – PagSeguro for WooCommerce Release Timeline

v2.14.0Current
v2.13.1
v2.13.0
v2.12.7
v2.12.6
v2.12.5
v2.12.4
v2.12.3
v2.12.2
v2.12.1
v2.12.0
Code Analysis
Analyzed Mar 16, 2026

Claudio Sanches – PagSeguro for WooCommerce Code Analysis

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

Output Escaping

92% escaped77 total outputs
Attack Surface

Claudio Sanches – PagSeguro for WooCommerce Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 12
actionwoocommerce_api_wc_pagseguro_gatewayincludes\class-wc-pagseguro-gateway.php:64
actionvalid_pagseguro_ipn_requestincludes\class-wc-pagseguro-gateway.php:65
actionwoocommerce_email_after_order_tableincludes\class-wc-pagseguro-gateway.php:72
actionwp_enqueue_scriptsincludes\class-wc-pagseguro-gateway.php:73
actioninitincludes\class-wc-pagseguro.php:18
filterwoocommerce_payment_gatewaysincludes\class-wc-pagseguro.php:24
filterwoocommerce_available_payment_gatewaysincludes\class-wc-pagseguro.php:25
filterwoocommerce_billing_fieldsincludes\class-wc-pagseguro.php:26
filterwoocommerce_shipping_fieldsincludes\class-wc-pagseguro.php:27
actionadmin_noticesincludes\class-wc-pagseguro.php:31
actionadmin_noticesincludes\class-wc-pagseguro.php:34
actionplugins_loadedwoocommerce-pagseguro.php:40
Maintenance & Trust

Claudio Sanches – PagSeguro for WooCommerce Maintenance & Trust

Maintenance Signals

WordPress version tested5.5.18
Last updatedAug 10, 2020
PHP min version
Downloads587K

Community Trust

Rating98/100
Number of ratings913
Active installs10K
Developer Profile

Claudio Sanches – PagSeguro for WooCommerce Developer Profile

Claudio Sanches

18 plugins · 134K total installs

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

How We Detect Claudio Sanches – PagSeguro for WooCommerce

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/woocommerce-pagseguro/assets/css/frontend/transparent-checkout.css/wp-content/plugins/woocommerce-pagseguro/assets/js/frontend/transparent-checkout.js
Script Paths
/wp-content/plugins/woocommerce-pagseguro/assets/js/frontend/transparent-checkout.js
Version Parameters
woocommerce-pagseguro/assets/css/frontend/transparent-checkout.css?ver=woocommerce-pagseguro/assets/js/frontend/transparent-checkout.js?ver=

HTML / DOM Fingerprints

CSS Classes
pagseguro-checkoutpagseguro-transparent-checkout
HTML Comments
<!-- Main actions --><!-- Transparent checkout actions --><!-- Set the API --><!-- Active logs -->+4 more
Data Attributes
data-pagseguro-session-iddata-pagseguro-interest-freedata-pagseguro-invalid-carddata-pagseguro-invalid-expirydata-pagseguro-expired-datedata-pagseguro-general-error+1 more
JS Globals
wc_pagseguro_params
FAQ

Frequently Asked Questions about Claudio Sanches – PagSeguro for WooCommerce