
Croatian payment slip generator for WooCommerce Security & Risk Analysis
wordpress.org/plugins/croatian-payment-slip-generator-for-woocommerceMake it easy for your customers from Croatia to perform direct bank transfer with generated payment slip, along with barcode for mBanking.
Is Croatian payment slip generator for WooCommerce Safe to Use in 2026?
Generally Safe
Score 85/100Croatian payment slip generator for WooCommerce has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The plugin "croatian-payment-slip-generator-for-woocommerce" v1.7.1 demonstrates a strong adherence to secure coding practices in several key areas. The absence of any registered CVEs, coupled with a complete lack of critical or high-severity vulnerabilities in its history, suggests a generally stable and well-maintained plugin. Furthermore, the static analysis shows a commendable absence of dangerous functions, external HTTP requests, and the presence of secure SQL queries using prepared statements. The plugin also correctly utilizes file operations securely and has no observed taint flows. However, there are significant areas of concern. The plugin lacks nonce checks entirely, and there are no capability checks implemented. This, combined with a concerningly low percentage of properly escaped output (29%), creates a substantial risk of cross-site scripting (XSS) and potential privilege escalation vulnerabilities, especially if any of the entry points, even though currently listed as zero, were to be introduced or discovered. The bundled Guzzle library, while not inherently a risk, should be regularly monitored for known vulnerabilities. The plugin's overall security posture is mixed, with excellent foundations in some aspects but critical oversights in input validation and authorization mechanisms that require immediate attention.
Key Concerns
- No Nonce Checks
- No Capability Checks
- Low Output Escaping Percentage
- Bundled Guzzle Library
Croatian payment slip generator for WooCommerce Security Vulnerabilities
Croatian payment slip generator for WooCommerce Release Timeline
Croatian payment slip generator for WooCommerce Code Analysis
Bundled Libraries
Output Escaping
Croatian payment slip generator for WooCommerce Attack Surface
WordPress Hooks 10
Maintenance & Trust
Croatian payment slip generator for WooCommerce Maintenance & Trust
Maintenance Signals
Community Trust
Croatian payment slip generator for WooCommerce Alternatives
KigoKasa Fiscalization for WooCommerce
kigokasa-api-for-woocommerce
This plugin provides integration of KigoKasa service with WooCommerce webshop.
Raskid ugovora na daljinu
raskid-ugovora-na-daljinu
Uskladite WooCommerce sa Zakonom o zaštiti potrošača: gumb za jednostrani raskid ugovora na daljinu, obvezan od 19. lipnja 2026.
Croatian Shipping for WooCommerce
croatian-shipping-for-woocommerce
Croatian Shipping methods for WooCommerce with restrictions. This plugin provides shipping methods available for Croatia.
H1Design Contract Withdrawal for WooCommerce
h1design-contract-withdrawal-for-woocommerce
Adds a compliant contract withdrawal button to WooCommerce orders, as required by Croatian consumer protection law (effective 19 June 2026).
Essential Addons for Elementor – Popular Elementor Templates & Widgets
essential-addons-for-elementor-lite
Elementor addon offering 120+ widgets and templates — Elementor Gallery, Slider, Form, Post Grid, Menu, Accordion, WooCommerce & more.
Croatian payment slip generator for WooCommerce Developer Profile
1 plugin · 300 total installs
How We Detect Croatian payment slip generator for WooCommerce
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/croatian-payment-slip-generator-for-woocommerce/assets/css/bootstrap-dropdown-button/bootstrap.css/wp-content/plugins/croatian-payment-slip-generator-for-woocommerce/assets/js/Popper.js/popper.min.js/wp-content/plugins/croatian-payment-slip-generator-for-woocommerce/assets/js/polyfills/polyfills.umd.min.js/wp-content/plugins/croatian-payment-slip-generator-for-woocommerce/assets/js/jsPDF/jspdf.umd.min.js/wp-content/plugins/croatian-payment-slip-generator-for-woocommerce/assets/js/bootstrap-dropdown-button/bootstrap.min.jscroatian-payment-slip-generator-for-woocommerce/assets/css/bootstrap-dropdown-button/bootstrap.css?ver=croatian-payment-slip-generator-for-woocommerce/assets/js/Popper.js/popper.min.js?ver=croatian-payment-slip-generator-for-woocommerce/assets/js/polyfills/polyfills.umd.min.js?ver=croatian-payment-slip-generator-for-woocommerce/assets/js/jsPDF/jspdf.umd.min.js?ver=croatian-payment-slip-generator-for-woocommerce/assets/js/bootstrap-dropdown-button/bootstrap.min.js?ver=HTML / DOM Fingerprints
wooplatnica-croatia<!-- add here default values of options that were introduced after initial version (a.k.a. version 1.0) of this plugin --><!-- this is useful because after updating plugin, options that didn't exist in previous version of plugin are not yet stored in the database, i.e. when those options would be fetched, their values would be null even if those newly defined options have defined default values in WC_Gateway_Wooplatnica.php, what resulted in unexcepted aad buggy behavior --><!-- Only remove ALL plugin settings data if WC_REMOVE_ALL_DATA constant is set to true in user's
* wp-config.php. This is to prevent data loss when deleting the plugin from the backend
* and to ensure only the site owner can perform this action. -->PDF417