CVE-2026-4782 is an authenticated arbitrary file read vulnerability in the Avada Builder plugin for WordPress affecting all versions up to and including 3.15.2. The flaw is present in the fusion_get_svg_from_file function when processing the custom_svg parameter of the fusion_section_separator shortcode. Insufficient validation of attacker-controlled file input allows a low-privileged authenticated user to cause the plugin to read arbitrary files from the server filesystem. The issue can expose sensitive local files accessible to the web server context, including application configuration data and other secrets. Version 3.15.2 only partially addressed the issue; the vulnerability was fully remediated in version 3.15.3.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Repository contains a single Python exploit script and a minimal README. The script targets CVE-2026-4782 in Avada Builder <= 3.15.2 on WordPress. Its primary purpose is to exploit a path traversal/arbitrary file read flaw in the fusion_form_submit_ajax handler by sending crafted POST requests to /wp-admin/admin-ajax.php with an attachment parameter containing traversal sequences and a target filename. The code includes built-in target files of interest such as wp-config.php, .env, and WordPress core files, along with multiple traversal encodings to improve reliability. Operational flow is: fetch a nonce from the target page or /wp-json/; optionally authenticate to WordPress via /wp-login.php using supplied credentials; then submit the malicious AJAX request. The script supports single-target and multi-target modes, custom nonce, custom traversal string, custom file target, proxying, timeout control, SSL verification disabling, and output logging. CLI help also indicates an SSRF test mode that reuses the attachment field with a remote URL, suggesting the vulnerable handler may also dereference external resources depending on target behavior. This is a real exploit rather than a detector: it attempts to retrieve file contents from the target and is designed for practical use against live WordPress/Avada installations. The repository is small, self-contained, and centered entirely around the Python entry point CVE-2026-4782.py.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An arbitrary file read vulnerability in Avada Builder mentioned as a related issue in the same release cycle; fully remediated in version 3.15.3 according to the content.
An arbitrary file read vulnerability in the Avada Builder WordPress plugin that allows authenticated low-privilege users to read sensitive server files via the custom_svg parameter.
An arbitrary file read vulnerability in the Avada Builder WordPress plugin that requires subscriber-level access and could allow unauthorized access to sensitive user data.
An arbitrary file read vulnerability in the Avada Builder WordPress plugin that could allow attackers with subscriber-level access to exfiltrate sensitive data.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.