PortOne for WooCommerce Security & Risk Analysis

wordpress.org/plugins/chaiport-payment

Allows you to use PortOne payment platform with the WooCommerce plugin.

10 active installs v3.1.1 PHP 5.6+ WP 5.6+ Updated Aug 8, 2025
chaipaychaiportecommercepaymentswoocommerce
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is PortOne for WooCommerce Safe to Use in 2026?

Generally Safe

Score 100/100

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

No known CVEs Updated 9mo ago
Risk Assessment

The chaiport-payment plugin v3.1.1 presents a significant security risk primarily due to its exposed attack surface. All three identified REST API routes lack permission callbacks, meaning any authenticated user could potentially interact with them without proper authorization checks. While the plugin avoids dangerous functions and uses prepared statements for SQL, the absence of capability checks on these entry points is a major concern. The plugin also shows no record of past vulnerabilities, which is generally a positive sign. However, this could also indicate a lack of thorough security auditing in the past, or that it has not been widely targeted. The static analysis also reveals that 67% of outputs are properly escaped, which is a reasonable rate but still leaves a portion potentially vulnerable to cross-site scripting (XSS) if user-supplied data is involved in unescaped outputs.

Key Concerns

  • REST API routes without permission callbacks
  • Partial output escaping (33% unescaped)
  • No nonce checks on AJAX handlers
Vulnerabilities
None known

PortOne for WooCommerce Security Vulnerabilities

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

PortOne for WooCommerce Release Timeline

v3.1.1Current
v3.1.0
v3.0.0
v2.0.9
v2.0.8
v2.0.7
v2.0.6
v2.0.5
v2.0.4
v2.0.3
v2.0.2
v2.0.1
v1.0.7
v1.0.6
v1.0.5
v1.0.4
v1.0.3
v1.0.2
v1.0.1
v1.0.0
Code Analysis
Analyzed Apr 16, 2026

PortOne for WooCommerce Code Analysis

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

Output Escaping

67% escaped12 total outputs
Attack Surface
3 unprotected

PortOne for WooCommerce Attack Surface

Entry Points3
Unprotected3

REST API Routes 3

GET/wp-json/portone/redirectchaiportGateway.php:269
GET/wp-json/chaiport/v1webhookchaiportGateway.php:300
GET/wp-json/portone/webhookchaiportGateway.php:305
WordPress Hooks 11
filterwoocommerce_payment_gatewayschaiportGateway.php:18
filterwoocommerce_my_account_my_orders_actionschaiportGateway.php:40
filterhandle_bulk_actions-edit-shop_orderchaiportGateway.php:87
actionrest_api_initchaiportGateway.php:268
actionplugins_loadedchaiportGateway.php:524
actionbefore_woocommerce_initchaiportGateway.php:528
actionwoocommerce_blocks_loadedchaiportGateway.php:529
actionwoocommerce_update_options_payment_gatewayschaiportGateway.php:578
actionwp_enqueue_scriptschaiportGateway.php:585
actionadmin_noticeschaiportGateway.php:588
actionwoocommerce_blocks_payment_method_type_registrationchaiportGateway.php:1336
Maintenance & Trust

PortOne for WooCommerce Maintenance & Trust

Maintenance Signals

WordPress version tested6.5.8
Last updatedAug 8, 2025
PHP min version5.6
Downloads5K

Community Trust

Rating0/100
Number of ratings0
Active installs10
Developer Profile

PortOne for WooCommerce Developer Profile

PortOne

1 plugin · 10 total installs

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

How We Detect PortOne for WooCommerce

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

Asset Fingerprints

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about PortOne for WooCommerce