<?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-18T07:16:01.679624+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-127220</id>
    <title>CVE-2026-127220 — Kadence Security WordPress Plugin &lt; 10.0.6.1 IPv6 Lockout Bypass</title>
    <updated>2026-11-18T07:16:01.680813+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Nexcess Kadence Security – Password, Two Factor Authentication, and Brute Force Protection</p>
<p>Kadence Security plugin for WordPress (better-wp-security) before 10.0.6.1 contains a brute-force protection bypass vulnerability that allows unauthenticated attackers to evade per-host login lockouts by exploiting IPv6 address handling in ITSEC_Lib::get_ip(), which keys failed-login counters on the full 128-bit IPv6 address rather than a /64 prefix. Attackers who control a routed IPv6 /64 can send each login attempt from a new address within that prefix, resetting the per-host counter each time to perform password spraying and username enumeration, and can similarly evade the auto_ban_admin immediate ban via address rotation.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-127220"/>
  </entry>
</feed>
