<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: ultimate addons for contact form 7</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-6756: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the </title><link>https://patchthecve.com/cve/CVE-2025-6756.html</link><guid>https://patchthecve.com/cve/CVE-2025-6756.html</guid><pubDate>Wed, 17 Jun 2026 10:02:30 +0000</pubDate><description>MEDIUM 6.4: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin&#x27;s UACF7_CUSTOM_FIELDS shortcode in all versions up to, and including, 3.5.21 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it poss</description></item><item><title>CVE-2025-6212: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the </title><link>https://patchthecve.com/cve/CVE-2025-6212.html</link><guid>https://patchthecve.com/cve/CVE-2025-6212.html</guid><pubDate>Wed, 17 Jun 2026 10:01:23 +0000</pubDate><description>HIGH 7.2: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Database module in versions 3.5.11 to 3.5.19 due to insufficient input sanitization and output escaping. The unfiltered field names are stored alongside the sanitized values. Later, the admi</description></item><item><title>CVE-2025-6220: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to arbitrary file uploads due to missin</title><link>https://patchthecve.com/cve/CVE-2025-6220.html</link><guid>https://patchthecve.com/cve/CVE-2025-6220.html</guid><pubDate>Wed, 17 Jun 2026 10:01:24 +0000</pubDate><description>HIGH 7.2: The Ultra Addons for Contact Form 7 plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the &#x27;save_options&#x27; function in all versions up to, and including, 3.5.12. This makes it possible for authenticated attackers, with Administrator-level access and ab</description></item></channel></rss>