<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: adamsolymosi</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-6024: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or email</title><link>https://patchthecve.com/cve/CVE-2024-6024.html</link><guid>https://patchthecve.com/cve/CVE-2024-6024.html</guid><pubDate>Wed, 17 Jun 2026 08:17:08 +0000</pubDate><description>HIGH 8.8: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when deleting groups or emails, which could allow attackers to make a logged in admin remove them via a CSRF attack</description></item><item><title>CVE-2024-6023: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which cou</title><link>https://patchthecve.com/cve/CVE-2024-6023.html</link><guid>https://patchthecve.com/cve/CVE-2024-6023.html</guid><pubDate>Wed, 17 Jun 2026 08:17:07 +0000</pubDate><description>HIGH 8.8: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when adding emails, which could allow attackers to make a logged in admin perform such action via a CSRF attack</description></item><item><title>CVE-2024-6022: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, w</title><link>https://patchthecve.com/cve/CVE-2024-6022.html</link><guid>https://patchthecve.com/cve/CVE-2024-6022.html</guid><pubDate>Wed, 17 Jun 2026 08:17:07 +0000</pubDate><description>HIGH 8.8: The ContentLock WordPress plugin through 1.0.3 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack</description></item></channel></rss>