<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: limit login attempts</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2023-1861: The Limit Login Attempts WordPress plugin through 1.7.2 does not sanitize and escape usernames when outputting</title><link>https://patchthecve.com/cve/CVE-2023-1861.html</link><guid>https://patchthecve.com/cve/CVE-2023-1861.html</guid><pubDate>Wed, 17 Jun 2026 05:28:54 +0000</pubDate><description>MEDIUM 5.4: The Limit Login Attempts WordPress plugin through 1.7.2 does not sanitize and escape usernames when outputting them back in the logs dashboard, which could allow any authenticated users, such as subscriber to perform Stored Cross-Site Scripting attacks</description></item><item><title>CVE-2023-1912: The Limit Login Attempts plugin for WordPress is vulnerable to Stored Cross-Site Scripting via its lock loggin</title><link>https://patchthecve.com/cve/CVE-2023-1912.html</link><guid>https://patchthecve.com/cve/CVE-2023-1912.html</guid><pubDate>Wed, 17 Jun 2026 05:29:01 +0000</pubDate><description>HIGH 7.2: 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 scr</description></item><item><title>CVE-2022-1029: The Limit Login Attempts WordPress plugin before 4.0.72 does not sanitise and escape some of its settings, lea</title><link>https://patchthecve.com/cve/CVE-2022-1029.html</link><guid>https://patchthecve.com/cve/CVE-2022-1029.html</guid><pubDate>Wed, 17 Jun 2026 04:21:40 +0000</pubDate><description>MEDIUM 4.8: The Limit Login Attempts WordPress plugin before 4.0.72 does not sanitise and escape some of its settings, leading to malicious users with administrator privileges to store malicious Javascript code leading to Cross-Site Scripting attacks when unfiltered_html is disallowed (for example in multisite </description></item></channel></rss>