<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: foogallery</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-6068: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is</title><link>https://patchthecve.com/cve/CVE-2025-6068.html</link><guid>https://patchthecve.com/cve/CVE-2025-6068.html</guid><pubDate>Wed, 17 Jun 2026 10:01:05 +0000</pubDate><description>MEDIUM 6.4: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `data-caption-title` &amp; `data-caption-description` HTML attributes in all versions up to, and including, 2.4.31 due to insufficient input sa</description></item><item><title>CVE-2024-12119: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is</title><link>https://patchthecve.com/cve/CVE-2024-12119.html</link><guid>https://patchthecve.com/cve/CVE-2024-12119.html</guid><pubDate>Wed, 17 Jun 2026 06:59:05 +0000</pubDate><description>MEDIUM 6.4: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the default_gallery_title_size parameter in all versions up to, and including, 2.4.29 due to insufficient input sanitization and output escapin</description></item><item><title>CVE-2024-12114: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is</title><link>https://patchthecve.com/cve/CVE-2024-12114.html</link><guid>https://patchthecve.com/cve/CVE-2024-12114.html</guid><pubDate>Wed, 17 Jun 2026 06:59:04 +0000</pubDate><description>MEDIUM 4.3: The FooGallery – Responsive Photo Gallery, Image Viewer, Justified, Masonry &amp; Carousel plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.4.29 via the foogallery_attachment_modal_save AJAX action due to missing validation on a user controll</description></item><item><title>CVE-2023-6947: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Directory Traversal in al</title><link>https://patchthecve.com/cve/CVE-2023-6947.html</link><guid>https://patchthecve.com/cve/CVE-2023-6947.html</guid><pubDate>Wed, 17 Jun 2026 06:51:44 +0000</pubDate><description>HIGH 7.7: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.4.26. This makes it possible for authenticated attackers, with contributor level or higher to read the contents of arbitrary folders on the server, which c</description></item><item><title>CVE-2024-2122: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripti</title><link>https://patchthecve.com/cve/CVE-2024-2122.html</link><guid>https://patchthecve.com/cve/CVE-2024-2122.html</guid><pubDate>Wed, 17 Jun 2026 07:23:46 +0000</pubDate><description>MEDIUM 6.4: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via album gallery custom URLs in all versions up to, and including, 2.4.15 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, </description></item><item><title>CVE-2024-2762: The FooGallery  WordPress plugin before 2.4.15, foogallery-premium WordPress plugin before 2.4.15 does not val</title><link>https://patchthecve.com/cve/CVE-2024-2762.html</link><guid>https://patchthecve.com/cve/CVE-2024-2762.html</guid><pubDate>Wed, 17 Jun 2026 07:25:29 +0000</pubDate><description>MEDIUM 5.4: The FooGallery  WordPress plugin before 2.4.15, foogallery-premium WordPress plugin before 2.4.15 does not validate and escape some of its Gallery settings before outputting them back in the page, which could allow users with a role as low as Author to perform Stored Cross-Site Scripting attacks whi</description></item><item><title>CVE-2024-2081: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripti</title><link>https://patchthecve.com/cve/CVE-2024-2081.html</link><guid>https://patchthecve.com/cve/CVE-2024-2081.html</guid><pubDate>Wed, 17 Jun 2026 07:23:41 +0000</pubDate><description>MEDIUM 6.4: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the foogallery_attachment_modal_save action in all versions up to, and including, 2.4.14 due to insufficient input sanitization and output escaping. This makes it possible for authent</description></item><item><title>CVE-2024-2471: The FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image attachment fields (</title><link>https://patchthecve.com/cve/CVE-2024-2471.html</link><guid>https://patchthecve.com/cve/CVE-2024-2471.html</guid><pubDate>Wed, 17 Jun 2026 07:24:36 +0000</pubDate><description>MEDIUM 6.4: The FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via image attachment fields (such as &#x27;Title&#x27;, &#x27;Alt Text&#x27;, &#x27;Custom URL&#x27;, &#x27;Custom Class&#x27;, and &#x27;Override Type&#x27;) in all versions up to, and including, 2.4.14 due to insufficient input sanitization and output escaping. This </description></item><item><title>CVE-2024-0604: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripti</title><link>https://patchthecve.com/cve/CVE-2024-0604.html</link><guid>https://patchthecve.com/cve/CVE-2024-0604.html</guid><pubDate>Wed, 17 Jun 2026 06:53:52 +0000</pubDate><description>MEDIUM 4.4: The Best WordPress Gallery Plugin – FooGallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 2.4.7 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with adminis</description></item></channel></rss>