<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: woostify</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-4788: The Boostify Header Footer Builder for Elementor plugin for WordPress is vulnerable to unauthorized modificati</title><link>https://patchthecve.com/cve/CVE-2024-4788.html</link><guid>https://patchthecve.com/cve/CVE-2024-4788.html</guid><pubDate>Wed, 17 Jun 2026 08:02:54 +0000</pubDate><description>MEDIUM 4.3: The Boostify Header Footer Builder for Elementor plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the create_bhf_post function in all versions up to, and including, 1.3.5. This makes it possible for authenticated attackers, with subscriber-</description></item><item><title>CVE-2024-5006: The Boostify Header Footer Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scrip</title><link>https://patchthecve.com/cve/CVE-2024-5006.html</link><guid>https://patchthecve.com/cve/CVE-2024-5006.html</guid><pubDate>Wed, 17 Jun 2026 08:14:53 +0000</pubDate><description>MEDIUM 6.4: The Boostify Header Footer Builder for Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘size’ parameter in all versions up to, and including, 1.3.2 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with</description></item><item><title>CVE-2023-6279: The Woostify Sites Library WordPress plugin before 1.4.8 does not have authorisation in an AJAX action, allowi</title><link>https://patchthecve.com/cve/CVE-2023-6279.html</link><guid>https://patchthecve.com/cve/CVE-2023-6279.html</guid><pubDate>Wed, 17 Jun 2026 06:50:27 +0000</pubDate><description>HIGH 7.1: The Woostify Sites Library WordPress plugin before 1.4.8 does not have authorisation in an AJAX action, allowing any authenticated users, such as subscriber to update arbitrary blog options and set them to &#x27;activated&#x27; which could lead to DoS when using a specific option name</description></item></channel></rss>