<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: branda</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-37239: Improper Neutralization of Input During Web Page Generation (&#x27;Cross-site Scripting&#x27;) vulnerability in WPMU DEV</title><link>https://patchthecve.com/cve/CVE-2024-37239.html</link><guid>https://patchthecve.com/cve/CVE-2024-37239.html</guid><pubDate>Wed, 17 Jun 2026 07:37:59 +0000</pubDate><description>MEDIUM 5.9: Improper Neutralization of Input During Web Page Generation (&#x27;Cross-site Scripting&#x27;) vulnerability in WPMU DEV - Your All-in-One WordPress Platform Branda branda-white-labeling.This issue affects Branda: from n/a through &lt;= 3.4.17.</description></item><item><title>CVE-2024-6554: The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Pa</title><link>https://patchthecve.com/cve/CVE-2024-6554.html</link><guid>https://patchthecve.com/cve/CVE-2024-6554.html</guid><pubDate>Wed, 17 Jun 2026 08:18:14 +0000</pubDate><description>MEDIUM 5.3: The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.4.18. This is due the plugin utilizing composer without preventing direct access to the files. This makes it possible for unauthenticate</description></item><item><title>CVE-2024-5191: The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Stored </title><link>https://patchthecve.com/cve/CVE-2024-5191.html</link><guid>https://patchthecve.com/cve/CVE-2024-5191.html</guid><pubDate>Wed, 17 Jun 2026 08:15:22 +0000</pubDate><description>MEDIUM 6.4: The Branda – White Label WordPress, Custom Login Page Customizer plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘mime_types’ parameter in all versions up to, and including, 3.4.17 due to insufficient input sanitization and output escaping. This makes it possible for authen</description></item></channel></rss>