
QR Module Security & Risk Analysis
wordpress.org/plugins/qr-invoiceWith this plugin you can create QR payment parts or even complete QR invoices according to the official Swiss specifications.
Is QR Module Safe to Use in 2026?
Generally Safe
Score 85/100QR Module has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.
The qr-invoice plugin v1.0.10 exhibits a concerning security posture due to its significant attack surface with unprotected entry points. The static analysis reveals two AJAX handlers that lack any authentication checks, presenting a direct pathway for unauthenticated users to interact with plugin functionalities. While the plugin demonstrates good practices in other areas, such as using prepared statements for all SQL queries and a high percentage of properly escaped output, these strengths are overshadowed by the critical lack of access control on its AJAX endpoints.
The absence of capability checks and nonce verification on these AJAX handlers is a major red flag. This means any visitor to a WordPress site running this plugin, even an unauthenticated one, could potentially trigger these functions, leading to unpredictable behavior or, in the worst-case scenario, exploitable vulnerabilities if the functions themselves handle user-supplied data insecurely. Although no specific taint flows were identified in the static analysis, the presence of unprotected entry points significantly increases the likelihood of such flows being exploited if they were to exist.
The plugin's vulnerability history is remarkably clean, with no recorded CVEs. This could indicate a history of secure development or simply a lack of targeted security research against this specific plugin. However, the absence of past vulnerabilities should not be seen as a guarantee of future security, especially given the current findings of unprotected entry points. In conclusion, while the plugin adheres to good practices regarding SQL and output escaping, the critical flaw of unprotected AJAX handlers makes it a high-risk plugin that requires immediate attention and remediation.
Key Concerns
- AJAX handlers without auth checks
- No nonce checks on AJAX handlers
- No capability checks
QR Module Security Vulnerabilities
QR Module Release Timeline
QR Module Code Analysis
Output Escaping
QR Module Attack Surface
AJAX Handlers 2
WordPress Hooks 11
Maintenance & Trust
QR Module Maintenance & Trust
Maintenance Signals
Community Trust
QR Module Alternatives
No alternatives data available yet.
QR Module Developer Profile
1 plugin · 10 total installs
How We Detect QR Module
Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.
Asset Fingerprints
/wp-content/plugins/qr-invoice/assets/css/wqrmi-admin-style.css/wp-content/plugins/qr-invoice/assets/js/wqrmi-script.js/wp-content/plugins/qr-invoice/assets/js/wqrmi-script.jsqr-invoice/assets/css/wqrmi-admin-style.css?ver=qr-invoice/assets/js/wqrmi-script.js?ver=HTML / DOM Fingerprints
wqrmi-settings-page<!-- QR Invoice Plugin Settings -->data-client-iddata-client-secretdata-token-durationwqrmi_ajax_object/wp-json/qr-invoice/v1/auth