Payment Checkout PagSeguro for LifterLMS Security & Risk Analysis

wordpress.org/plugins/payment-checkout-pagseguro-for-lifterlms

Enable PagSeguro Checkout payment (include debit card, credit card, bank slip, payment with account balance, etc) for LifterLMS.

0 active installs v2.0.7 PHP 7.2+ WP 5.5+ Updated Unknown
creditdebitlifterlmspagbankpagseguro
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Payment Checkout PagSeguro for LifterLMS Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs
Risk Assessment

The plugin "payment-checkout-pagseguro-for-lifterlms" v2.0.7 exhibits a generally good security posture due to the absence of dangerous functions, 100% properly escaped output, and the use of prepared statements for all SQL queries. The plugin also has no recorded vulnerability history, which is a positive indicator. However, a significant concern arises from the presence of a single unprotected REST API route, representing a clear attack vector that could be exploited without proper authentication or authorization checks. The lack of nonce checks and capability checks further amplifies this risk, as there are no mechanisms to verify user intent or permissions for this entry point.

The static analysis reveals a total of one unprotected entry point, specifically the REST API route. This is the primary area of concern. The absence of taint analysis findings suggests that at this version, known data flow vulnerabilities are not present, but this does not mitigate the direct risk of the unprotected endpoint. The plugin's strengths lie in its secure handling of SQL and output, but the single exposed REST API route is a critical weakness that requires immediate attention to prevent potential unauthorized access or manipulation of functionality.

Key Concerns

  • Unprotected REST API route
  • REST API route without permission callbacks
  • Missing nonce checks
  • Missing capability checks
Vulnerabilities
None known

Payment Checkout PagSeguro for LifterLMS Security Vulnerabilities

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

Payment Checkout PagSeguro for LifterLMS Code Analysis

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

Output Escaping

100% escaped15 total outputs
Attack Surface
1 unprotected

Payment Checkout PagSeguro for LifterLMS Attack Surface

Entry Points1
Unprotected1

REST API Routes 1

POST/wp-json/lknLifterPagseguro/v1/listenerincludes\class-payment-checkout-pagseguro-for-lifterlms.php:133
WordPress Hooks 10
actionadmin_noticesincludes\class-payment-checkout-pagseguro-for-lifterlms-helper.php:119
actionadmin_noticesincludes\class-payment-checkout-pagseguro-for-lifterlms-helper.php:123
actionplugins_loadedincludes\class-payment-checkout-pagseguro-for-lifterlms.php:149
actionwp_enqueue_scriptsincludes\class-payment-checkout-pagseguro-for-lifterlms.php:162
filterlifterlms_payment_gatewaysincludes\class-payment-checkout-pagseguro-for-lifterlms.php:164
actionrest_api_initincludes\class-payment-checkout-pagseguro-for-lifterlms.php:165
actioninitincludes\class-payment-checkout-pagseguro-for-lifterlms.php:166
filterllms_get_gateway_settings_fieldspublic\class-lkn-payment-checkout-pagseguro-for-lifterlms-gateway.php:39
actionlifterlms_before_view_order_tablepublic\class-lkn-payment-checkout-pagseguro-for-lifterlms-gateway.php:41
actionlifterlms_after_view_order_tablepublic\class-lkn-payment-checkout-pagseguro-for-lifterlms-gateway.php:42
Maintenance & Trust

Payment Checkout PagSeguro for LifterLMS Maintenance & Trust

Maintenance Signals

WordPress version tested6.9.4
Last updatedUnknown
PHP min version7.2
Downloads262

Community Trust

Rating100/100
Number of ratings1
Active installs0
Developer Profile

Payment Checkout PagSeguro for LifterLMS Developer Profile

linknacional

18 plugins · 5K total installs

99
trust score
Avg Security Score
98/100
Avg Patch Time
6 days
View full developer profile
Detection Fingerprints

How We Detect Payment Checkout PagSeguro for LifterLMS

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/payment-checkout-pagseguro-for-lifterlms/includes/js/payment-checkout-pagseguro-for-lifterlms-admin-settings.js/wp-content/plugins/payment-checkout-pagseguro-for-lifterlms/includes/css/payment-checkout-pagseguro-for-lifterlms-admin.css
Script Paths
/wp-content/plugins/payment-checkout-pagseguro-for-lifterlms/includes/js/payment-checkout-pagseguro-for-lifterlms-admin-settings.js
Version Parameters
payment-checkout-pagseguro-for-lifterlms/includes/js/payment-checkout-pagseguro-for-lifterlms-admin-settings.js?ver=payment-checkout-pagseguro-for-lifterlms/includes/css/payment-checkout-pagseguro-for-lifterlms-admin.css?ver=

HTML / DOM Fingerprints

CSS Classes
lkn-payment-checkout-pagseguro-for-lifterlms-admin-settings
HTML Comments
<!-- Enabled by Payment Checkout PagSeguro for LifterLMS -->
Data Attributes
data-gateway-id="pagseguro-v1"data-lifter-gateway-option-name="pagseguro-v1-payment_instructions"data-lifter-gateway-option-name="pagseguro-v1-email"data-lifter-gateway-option-name="pagseguro-v1-env_type"data-lifter-gateway-option-name="pagseguro-v1-token_key"
JS Globals
lknPaymentCheckoutPagseguroForLifterlmsPhpVariables
FAQ

Frequently Asked Questions about Payment Checkout PagSeguro for LifterLMS