
Bluesnap for WordPress Security & Risk Analysis
wordpress.org/plugins/plimus-for-wordpressPlimus for WordPress allows seamless Bluesnap Payment Gateway IPN integration for WordPress blogs.
Is Bluesnap for WordPress Safe to Use in 2026?
Generally Safe
Score 100/100Bluesnap for WordPress has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The security posture of the "plimus-for-wordpress" v1.1.3 plugin presents a mixed bag of good practices and significant concerns. On the positive side, the plugin has no known CVEs, indicating a relatively clean history. Furthermore, its limited attack surface with zero AJAX handlers, REST API routes, shortcodes, or cron events that are accessible without authentication is a strong point. The absence of external HTTP requests and a focus on file operations rather than direct user interaction in those areas can also be seen as positive security considerations.
However, the static analysis reveals critical areas of weakness. The most concerning finding is that 0% of the 30 total outputs are properly escaped. This opens the door to potential cross-site scripting (XSS) vulnerabilities, where malicious code could be injected and executed in users' browsers. Additionally, while 44% of SQL queries use prepared statements, a significant portion still does not, posing a risk of SQL injection if these queries handle user-supplied input without proper sanitization. The presence of 3 taint flows with unsanitized paths, even without a critical or high severity classification, suggests potential pathways for data to be misused or lead to unexpected behavior.
The lack of nonce checks and capability checks, combined with the absence of authentication on any identified entry points (even though the number of entry points is zero), suggests a potential oversight in securing actions that might be triggered indirectly. The use of a very outdated jQuery v1.4.3 library is another significant concern, as older library versions are often known to contain security vulnerabilities that have since been patched in newer releases. In conclusion, while the plugin avoids common pitfalls like numerous unauthenticated entry points or known CVEs, the severe lack of output escaping, potential for SQL injection, and outdated bundled library present substantial security risks that require immediate attention.
Key Concerns
- Outputs are not properly escaped
- SQL queries are not always prepared
- Taint flows with unsanitized paths
- Bundled outdated library (jQuery v1.4.3)
- No nonce checks implemented
- No capability checks implemented
Bluesnap for WordPress Security Vulnerabilities
Bluesnap for WordPress Code Analysis
Bundled Libraries
SQL Query Safety
Output Escaping
Data Flow Analysis
Bluesnap for WordPress Attack Surface
WordPress Hooks 3
Maintenance & Trust
Bluesnap for WordPress Maintenance & Trust
Maintenance Signals
Community Trust
Bluesnap for WordPress Alternatives
WorldPay Hosted Payment Gateway
woo-worldpay-hosted-payment-gateway
Custom worldpay payment gateway for your woocommerce based site.
WP Invoices Ultimate
wp-invoice-ultimate
Simple to use invoicing system that can intergrate with Paypal. Very simple, very flexble.
Loginizer
loginizer
Loginizer is a WordPress security plugin which helps you fight against bruteforce attacks.
Redux Framework
redux-framework
Redux is a simple, truly extensible, and fully responsive options framework for WordPress themes and plugins. It ships with an integrated demo.
WooPayments: Integrated WooCommerce Payments
woocommerce-payments
Securely accept credit and debit cards on your WooCommerce store. Manage payments without leaving your WordPress dashboard. Only with WooPayments.
Bluesnap for WordPress Developer Profile
20 plugins · 1.0M total installs
How We Detect Bluesnap for WordPress
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/plimus-for-wordpress/images/plimus_logo.png/wp-content/plugins/plimus-for-wordpress/images/pn_plugin_icon.pngHTML / DOM Fingerprints
plimus-logoid="plimus-logo"