<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: odude</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-9990: The Crypto plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, </title><link>https://patchthecve.com/cve/CVE-2024-9990.html</link><guid>https://patchthecve.com/cve/CVE-2024-9990.html</guid><pubDate>Wed, 17 Jun 2026 08:25:39 +0000</pubDate><description>HIGH 8.8: The Crypto plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.15. This is due to missing nonce validation in the &#x27;crypto_connect_ajax_process::check&#x27; function. This makes it possible for unauthenticated attackers to log in as any existing user on the</description></item><item><title>CVE-2024-9989: The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.18</title><link>https://patchthecve.com/cve/CVE-2024-9989.html</link><guid>https://patchthecve.com/cve/CVE-2024-9989.html</guid><pubDate>Wed, 17 Jun 2026 08:25:39 +0000</pubDate><description>CRITICAL 9.8: The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.18. This is due to a limited arbitrary method call to &#x27;crypto_connect_ajax_process::log_in&#x27; function in the &#x27;crypto_connect_ajax_process&#x27; function. This makes it possible for unauthenticated at</description></item><item><title>CVE-2024-9988: The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.19</title><link>https://patchthecve.com/cve/CVE-2024-9988.html</link><guid>https://patchthecve.com/cve/CVE-2024-9988.html</guid><pubDate>Wed, 17 Jun 2026 08:25:39 +0000</pubDate><description>CRITICAL 9.8: The Crypto plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 2.19. This is due to missing validation on the user being supplied in the &#x27;crypto_connect_ajax_process::register&#x27; function. This makes it possible for unauthenticated attackers to log in as any e</description></item></channel></rss>