<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: stellarwp</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-5144: The The Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-date-*</title><link>https://patchthecve.com/cve/CVE-2025-5144.html</link><guid>https://patchthecve.com/cve/CVE-2025-5144.html</guid><pubDate>Wed, 17 Jun 2026 09:47:19 +0000</pubDate><description>MEDIUM 6.4: The The Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘data-date-*’ parameters in all versions up to, and including, 6.13.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-lev</description></item><item><title>CVE-2024-8493: The Events Calendar WordPress plugin before 6.6.4 does not sanitise and escape some of its settings, which cou</title><link>https://patchthecve.com/cve/CVE-2024-8493.html</link><guid>https://patchthecve.com/cve/CVE-2024-8493.html</guid><pubDate>Wed, 17 Jun 2026 08:22:44 +0000</pubDate><description>MEDIUM 4.8: The Events Calendar WordPress plugin before 6.6.4 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 (for example in multisite setup).</description></item><item><title>CVE-2024-5333: The Events Calendar WordPress plugin before 6.8.2.1 is missing access checks in the REST API, allowing for una</title><link>https://patchthecve.com/cve/CVE-2024-5333.html</link><guid>https://patchthecve.com/cve/CVE-2024-5333.html</guid><pubDate>Wed, 17 Jun 2026 08:15:42 +0000</pubDate><description>MEDIUM 5.3: The Events Calendar WordPress plugin before 6.8.2.1 is missing access checks in the REST API, allowing for unauthenticated users to access information about password protected events.</description></item><item><title>CVE-2024-10939: The Image Widget WordPress plugin before 4.4.11 does not sanitise and escape some of its Image Widget settings</title><link>https://patchthecve.com/cve/CVE-2024-10939.html</link><guid>https://patchthecve.com/cve/CVE-2024-10939.html</guid><pubDate>Wed, 17 Jun 2026 06:56:44 +0000</pubDate><description>MEDIUM 4.8: The Image Widget WordPress plugin before 4.4.11 does not sanitise and escape some of its Image Widget 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 (for example in multisite setup).</description></item><item><title>CVE-2024-6931: The The Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via RSVP name field </title><link>https://patchthecve.com/cve/CVE-2024-6931.html</link><guid>https://patchthecve.com/cve/CVE-2024-6931.html</guid><pubDate>Wed, 17 Jun 2026 08:19:00 +0000</pubDate><description>HIGH 7.2: The The Events Calendar plugin for WordPress is vulnerable to Stored Cross-Site Scripting via RSVP name field in all versions up to, and including, 6.6.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts i</description></item><item><title>CVE-2024-8275: The The Events Calendar plugin for WordPress is vulnerable to SQL Injection via the &#x27;order&#x27; parameter of the &#x27;</title><link>https://patchthecve.com/cve/CVE-2024-8275.html</link><guid>https://patchthecve.com/cve/CVE-2024-8275.html</guid><pubDate>Wed, 17 Jun 2026 08:22:14 +0000</pubDate><description>CRITICAL 9.8: The The Events Calendar plugin for WordPress is vulnerable to SQL Injection via the &#x27;order&#x27; parameter of the &#x27;tribe_has_next_event&#x27; function in all versions up to, and including, 6.6.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL </description></item></channel></rss>