<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: cards for beaver builder</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2024-37278: Improper Neutralization of Input During Web Page Generation (XSS or &#x27;Cross-site Scripting&#x27;) vulnerability in P</title><link>https://patchthecve.com/cve/CVE-2024-37278.html</link><guid>https://patchthecve.com/cve/CVE-2024-37278.html</guid><pubDate>Wed, 17 Jun 2026 07:38:03 +0000</pubDate><description>MEDIUM 5.9: Improper Neutralization of Input During Web Page Generation (XSS or &#x27;Cross-site Scripting&#x27;) vulnerability in Pratik Chaskar Cards for Beaver Builder.This issue affects Cards for Beaver Builder: from n/a through 1.1.4.</description></item><item><title>CVE-2024-5663: The Cards for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin&#x27;</title><link>https://patchthecve.com/cve/CVE-2024-5663.html</link><guid>https://patchthecve.com/cve/CVE-2024-5663.html</guid><pubDate>Wed, 17 Jun 2026 08:16:23 +0000</pubDate><description>MEDIUM 6.4: The Cards for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin&#x27;s Cards widget in all versions up to, and including, 1.1.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated at</description></item><item><title>CVE-2024-2305: The Cards for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Bootstr</title><link>https://patchthecve.com/cve/CVE-2024-2305.html</link><guid>https://patchthecve.com/cve/CVE-2024-2305.html</guid><pubDate>Wed, 17 Jun 2026 07:24:16 +0000</pubDate><description>MEDIUM 6.4: The Cards for Beaver Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the BootstrapCard link  in all versions up to, and including, 1.1.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated atta</description></item></channel></rss>