<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: trumani</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2023-2489: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2023 does not sanitise </title><link>https://patchthecve.com/cve/CVE-2023-2489.html</link><guid>https://patchthecve.com/cve/CVE-2023-2489.html</guid><pubDate>Wed, 17 Jun 2026 05:52:42 +0000</pubDate><description>MEDIUM 4.8: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2023 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (f</description></item><item><title>CVE-2023-2488: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2023 does not sanitise </title><link>https://patchthecve.com/cve/CVE-2023-2488.html</link><guid>https://patchthecve.com/cve/CVE-2023-2488.html</guid><pubDate>Wed, 17 Jun 2026 05:52:42 +0000</pubDate><description>MEDIUM 6.1: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2023 does not sanitise and escape various parameters before outputting them back in admin dashboard pages, leading to a Reflected Cross-Site Scripting which could be used against high privilege users such as admin</description></item><item><title>CVE-2022-4120: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2022.6 passes base64 en</title><link>https://patchthecve.com/cve/CVE-2022-4120.html</link><guid>https://patchthecve.com/cve/CVE-2022-4120.html</guid><pubDate>Wed, 17 Jun 2026 05:20:00 +0000</pubDate><description>CRITICAL 9.8: The Stop Spammers Security | Block Spam Users, Comments, Forms WordPress plugin before 2022.6 passes base64 encoded user input to the unserialize() PHP function when CAPTCHA are used as second challenge, which could lead to PHP Object injection if a plugin installed on the blog has a suitable gadget</description></item></channel></rss>