¿Es seguro Limit Login Attempts?

Qué hace este plugin

• Slug: limit-login-attempts
• 300000+ instalaciones activas

authenticationloginsecurity

Estado de mantenimiento

• Última versión conocida: 1.7.2
• PHP máximo soportado (analizado): 8.4

Vulnerabilidades conocidas

4 CVEs conocidos registrados para Limit Login Attempts.

CVE-2023-1861

Update the WordPress Limit Login Attempts plugin to the latest available version (at least 1.7.2). Marc-Alexandre Montpas discovered and reported this Cross Site Scripting (XSS) vulnerability in WordPress Limit Login Attempts Plugin. This could allow a malicious actor to inject malicious scripts, such as redirects, advertisements, and other HTML payloads into your website which will be executed when guests visit your site. This vulnerability has been fixed in version 1.7.2.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: Patchstack

CVE-2023-1912

The Limit Login Attempts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via its lock logging feature in versions up to, and including, 1.7.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever an administrator accesses the plugin's settings page. This only works when the plugin prioritizes use of the X-FORWARDED-FOR header, which can be configured in its settings.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: CVE.org

CVE-2012-10001

From the changelog of the plugin: "Auth cookies" are special cookies set at login that authenticating you to the system. It is how WordPress "remembers" that you are logged in between page loads. During lockout these are supposed to be cleared, but a change in 1.6.2 broke this. It allowed an attacker to keep trying to break these cookies during a lockout. Lockout of normal password login attempts still worked as it should, and it appears that all "auth cookie" attempts would keep getting logged. In theory the "auth cookie" is quite resistant to brute force attack. It contains a cryptographic hash of the user password, and the difficulty to break it is not based on the password strength but instead on the cryptographic operations used and the length of the hash value. In theory it should take many many years to break this hash. As theory and practice does not always agree it is still a good idea to have working lockouts of any such attempts.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: WPScan

CVE-2023-40666

** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.

Descripción técnica mostrada en el idioma original de la fuente (inglés).

Fuente: CVE.org

Cómo solucionarlo

Mantén Limit Login Attempts actualizado — 1.7.2 es la última versión en wordpress.org, y cada CVE de arriba indica la versión exacta que lo corrigió ("Corregido en").

Este es el historial completo de vulnerabilidades conocidas del plugin, no un escaneo de una instalación específica — ejecuta un escaneo gratis de tu propio sitio para verificar tu versión instalada exacta.

Alternativas más seguras / más establecidas

• WPS Hide Login — 2000000+ instalaciones activas — 96/100 (2109) — PHP máx. 8.4
• Loginizer — 1000000+ instalaciones activas — 96/100 (1028) — PHP máx. <8.0
• Security Optimizer – The All-In-One Protection Plugin — 1000000+ instalaciones activas — 90/100 (155) — PHP máx. <8.0
• LoginPress | wp-login Custom Login Page Customizer — 200000+ instalaciones activas — 96/100 (1074) — PHP máx. 8.4
• WPS Limit Login — 100000+ instalaciones activas — 98/100 (83)