<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"
        xmlns:news="http://www.google.com/schemas/sitemap-news/0.9"
        xmlns:image="http://www.google.com/schemas/sitemap-image/1.1">
    <url>
        <loc>https://www.365i.co.uk/news/2026/05/15/avada-builder-sql-injection-cve-2026-4798/</loc>
        <news:news>
            <news:publication>
                <news:name>365i</news:name>
                <news:language>en-GB</news:language>
            </news:publication>
            <news:publication_date>2026-05-15T08:55:00+01:00</news:publication_date>
            <news:title>Avada Builder Just Patched a 1M-Site SQL Injection. The WooCommerce Deactivated Trap Is the Buried Lead.</news:title>
        </news:news>
        <image:image>
            <image:loc>https://www.365i.co.uk/images/posts/2026/05/avada-builder-sql-injection-cve-2026-4798-16x9.webp</image:loc>
            <image:title>Avada Builder Just Patched a 1M-Site SQL Injection. The WooCommerce Deactivated Trap Is the Buried Lead.</image:title>
            <image:caption>Wordfence disclosed CVE-2026-4798 in Avada Builder this week, affecting over 1,050,000 WordPress installations. The headline is patch to 3.15.3. The buried lead almost nobody covered is the WooCommerce-installed-then-deactivated precondition that turns the SQL injection from a "1M sites at risk" panic into a much narrower exploit window. We have held Avada licences for years and patched our portfolio first. Here is what actually matters.</image:caption>
        </image:image>
    </url>
</urlset>
