<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: name directory</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2023-22692: Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin &lt;= 1.27.1 versions.</title><link>https://patchthecve.com/cve/CVE-2023-22692.html</link><guid>https://patchthecve.com/cve/CVE-2023-22692.html</guid><pubDate>Wed, 17 Jun 2026 05:35:57 +0000</pubDate><description>MEDIUM 4.3: Cross-Site Request Forgery (CSRF) vulnerability in Jeroen Peters Name Directory plugin &lt;= 1.27.1 versions.</description></item><item><title>CVE-2022-2072: The Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting i</title><link>https://patchthecve.com/cve/CVE-2022-2072.html</link><guid>https://patchthecve.com/cve/CVE-2022-2072.html</guid><pubDate>Wed, 17 Jun 2026 04:41:14 +0000</pubDate><description>MEDIUM 6.1: The Name Directory WordPress plugin before 1.25.3 does not sanitise and escape a parameter before outputting it back in the page, leading to a Reflected Cross-Site Scripting. Furthermore, as the payload is also saved into the database after the request, it leads to a Stored XSS as well</description></item><item><title>CVE-2022-2071: The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also l</title><link>https://patchthecve.com/cve/CVE-2022-2071.html</link><guid>https://patchthecve.com/cve/CVE-2022-2071.html</guid><pubDate>Wed, 17 Jun 2026 04:41:14 +0000</pubDate><description>MEDIUM 6.1: The Name Directory WordPress plugin before 1.25.4 does not have CSRF check when importing names, and is also lacking sanitisation as well as escaping in some of the imported data, which could allow attackers to make a logged in admin import arbitrary names with XSS payloads in them.</description></item></channel></rss>