<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: sayandatta</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-6864: The WP Last Modified Info plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘template’</title><link>https://patchthecve.com/cve/CVE-2024-6864.html</link><guid>https://patchthecve.com/cve/CVE-2024-6864.html</guid><pubDate>Wed, 17 Jun 2026 08:18:52 +0000</pubDate><description>MEDIUM 6.4: The WP Last Modified Info plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘template’ attribute of the lmt-post-modified-info shortcode in all versions up to, and including, 1.9.0 due to insufficient input sanitization and output escaping. This makes it possible for authenti</description></item><item><title>CVE-2023-4725: The Simple Posts Ticker WordPress plugin before 1.1.6 does not sanitise and escape some of its settings, which</title><link>https://patchthecve.com/cve/CVE-2023-4725.html</link><guid>https://patchthecve.com/cve/CVE-2023-4725.html</guid><pubDate>Wed, 17 Jun 2026 06:38:27 +0000</pubDate><description>MEDIUM 4.8: The Simple Posts Ticker WordPress plugin before 1.1.6 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-2023-4646: The Simple Posts Ticker WordPress plugin before 1.1.6 does not validate and escape some of its shortcode attri</title><link>https://patchthecve.com/cve/CVE-2023-4646.html</link><guid>https://patchthecve.com/cve/CVE-2023-4646.html</guid><pubDate>Wed, 17 Jun 2026 06:38:17 +0000</pubDate><description>MEDIUM 5.4: The Simple Posts Ticker WordPress plugin before 1.1.6 does not validate and escape some of its shortcode attributes before outputting them back in a page/post where the shortcode is embed, which could allow users with the contributor role and above to perform Stored Cross-Site Scripting attacks.</description></item></channel></rss>