Failed Login Firewall reporting Security & Risk Analysis

wordpress.org/plugins/failed-login-firewall

Report failed logins to centralized database and block IPs on firewall level!

50 active installs v0.32 PHP + WP 3.0.1+ Updated Mar 3, 2022
apfcsffirewallloginsecurity
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Failed Login Firewall reporting Safe to Use in 2026?

Generally Safe

Score 85/100

Failed Login Firewall reporting has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 4yr ago
Risk Assessment

The plugin 'failed-login-firewall' v0.32 demonstrates a generally good security posture based on the static analysis. The absence of any attack surface points, dangerous functions, raw SQL queries, or identified taint flows is a significant strength. The plugin also boasts no known historical vulnerabilities, indicating a history of secure development or prompt patching.

However, there are notable areas for improvement. The most concerning finding is that 0% of the 2 total output escape checks passed. This suggests that data output by the plugin might not be properly sanitized, potentially leading to cross-site scripting (XSS) vulnerabilities if user-supplied data is included in the output. While the plugin only makes one external HTTP request, the lack of information on whether this request is secured or validated warrants further investigation.

In conclusion, 'failed-login-firewall' v0.32 has a solid foundation with no identified critical flaws in its entry points or data handling. The primary concern lies with output escaping, which needs immediate attention to prevent potential XSS attacks. The lack of historical vulnerabilities is a positive indicator, but the current output escaping issue introduces a tangible risk.

Key Concerns

  • Output escaping is not properly implemented
Vulnerabilities
None known

Failed Login Firewall reporting Security Vulnerabilities

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

Failed Login Firewall reporting Code Analysis

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

Output Escaping

0% escaped2 total outputs
Attack Surface

Failed Login Firewall reporting Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 4
actionadmin_menuclass.failed_login_firewall.admin.php:21
actionwp_login_failedclass.failed_login_firewall.php:21
actioninitfailed-login-firewall.php:26
actioninitfailed-login-firewall.php:33
Maintenance & Trust

Failed Login Firewall reporting Maintenance & Trust

Maintenance Signals

WordPress version tested5.9.13
Last updatedMar 3, 2022
PHP min version
Downloads2K

Community Trust

Rating100/100
Number of ratings2
Active installs50
Developer Profile

Failed Login Firewall reporting Developer Profile

Anton Aleksandrov

2 plugins · 4K total installs

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

How We Detect Failed Login Firewall reporting

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

Asset Fingerprints

Version Parameters
failed-login-firewall/style.css?ver=failed-login-firewall/script.js?ver=

HTML / DOM Fingerprints

FAQ

Frequently Asked Questions about Failed Login Firewall reporting