Paysley Security & Risk Analysis

wordpress.org/plugins/paysley

WHEN YOU NEED MORE THAN JUST A SHOPPING CART PAYMENT SOLUTION

10 active installs v2.0.4 PHP 7.4+ WP 5.0+ Updated Jun 22, 2024
apple-paycredit-cardgoogle-paypayment-methodpaysley
92
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Paysley Safe to Use in 2026?

Generally Safe

Score 92/100

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

No known CVEs Updated 1yr ago
Risk Assessment

Based on the provided static analysis and vulnerability history, the 'paysley' v2.0.4 plugin exhibits a strong security posture. The absence of any detected dangerous functions, raw SQL queries, file operations, or unsanitized taint flows is highly positive. Furthermore, all detected output is properly escaped, indicating good practices in preventing cross-site scripting (XSS) vulnerabilities. The plugin also avoids bundling external libraries, which can sometimes introduce their own security risks if not maintained. The vulnerability history being completely clear of any recorded CVEs further bolsters confidence in its current security state. However, the lack of nonce and capability checks on any entry points, combined with the absence of any detected entry points at all, presents a potential area for concern. While the current analysis shows no exposed functionalities, this could indicate an incomplete analysis or a plugin that has minimal functionality exposed to the public, making it difficult to assess broader risks.

Key Concerns

  • No capability checks detected
  • No nonce checks detected
Vulnerabilities
None known

Paysley Security Vulnerabilities

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

Paysley Code Analysis

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

Output Escaping

100% escaped2 total outputs
Attack Surface

Paysley Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 11
actionwoocommerce_before_thankyouincludes\class-paysley.php:60
actionwoocommerce_order_edit_statusincludes\class-paysley.php:62
actionwoocommerce_order_status_changedincludes\class-paysley.php:64
actionplugins_loadedpaysley.php:63
filterwoocommerce_payment_gatewayspaysley.php:75
filterquery_varspaysley.php:111
actionwoocommerce_new_productpaysley.php:113
actionwoocommerce_update_productpaysley.php:114
actionbefore_woocommerce_initpaysley.php:132
actionwoocommerce_blocks_loadedpaysley.php:136
actionwoocommerce_blocks_payment_method_type_registrationpaysley.php:149
Maintenance & Trust

Paysley Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedJun 22, 2024
PHP min version7.4
Downloads1K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

Paysley Developer Profile

Paysley

1 plugin · 10 total installs

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

How We Detect Paysley

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/paysley/assets/img/py-logo.png
Script Paths
/wp-content/plugins/paysley/includes/block/checkout.js
Version Parameters
paysley/includes/block/checkout.js?v=

HTML / DOM Fingerprints

JS Globals
paysley_settings
FAQ

Frequently Asked Questions about Paysley