<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-21T18:34:00.327403+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-127221</id>
    <title>CVE-2026-127221 — WPS Limit Login &lt; 1.5.9.5 Brute Force via IPv6 Address Rotation</title>
    <updated>2026-11-21T18:34:00.328588+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> NicolasKulka WPS Limit Login</p>
<p>WPS Limit Login (wps-limit-login) before 1.5.9.5 contains an improper access control vulnerability that allows unauthenticated attackers to bypass login lockout protections by keying the per-attempt login counter and lockout map on the raw, non-canonicalized IPv6 client address. Attackers controlling a routable IPv6 /64 prefix can send each login attempt from a fresh address within that range, preventing any counter from reaching the lockout threshold and enabling effectively unlimited brute-force password guessing against WordPress accounts.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-127221"/>
  </entry>
</feed>
