Atomic Edge analysis of CVE-2026-4782 (metadata-based): This vulnerability allows authenticated attackers with Subscriber-level access to read arbitrary files on the server via the Avada Builder plugin (slug: fusion-builder) up to version 3.15.2. The flaw exists in the ‘fusion_section_separator’ shortcode’s ‘custom_svg’ parameter, processed by the ‘fusion_get_svg_from_file’ function. The CVSS score of 6.5 (High) reflects low attack complexity and no user interaction, but requires authentication.
The root cause is an absolute path traversal vulnerability (CWE-36) in the ‘fusion_get_svg_from_file’ function. Atomic Edge analysis infers that the plugin fails to validate or sanitize the ‘custom_svg’ parameter, allowing an attacker to supply an absolute path (e.g., /etc/passwd) instead of a relative file reference. The function likely passes this path directly to file reading functions like file_get_contents() without checking whether the resolved path lies within an allowed directory. This inference is based on the CWE classification and the parameter name ‘custom_svg’, which suggests user-supplied file paths. No code diff is available to confirm the exact vulnerable logic.
Exploitation requires sending a crafted request to the WordPress AJAX handler or through the shortcode rendering. An attacker with Subscriber-level access can post a shortcode like [fusion_section_separator custom_svg=’/etc/passwd’] via a page or widget. If processed by the vulnerable function, the server reads the specified file and includes its contents in the rendered output. The attacker could also use the admin-ajax.php endpoint if the shortcode is registered as an AJAX action. The attack vector is network-based (AV:N) with low complexity, requiring only valid credentials (PR:L) and no user interaction.
Remediation requires the plugin to validate all file paths passed to ‘custom_svg’ to ensure they resolve within an allowed directory (e.g., the plugin’s svg assets folder). The fix should use realpath() to resolve the path and compare it against a whitelisted base path, rejecting any path that escapes that directory. Input sanitization and capability checks (e.g., ensure the user has ‘edit_pages’ capability for shortcode usage) would also help. The partial patch in 3.15.2 and full fix in 3.15.3 likely implement such path validation.
The impact is high for confidentiality (C:H in CVSS). An attacker can read sensitive server files including wp-config.php (database credentials), /etc/passwd (user enumeration), or other configuration files. This can lead to full site compromise if database credentials are obtained. The vulnerability does not allow modification or deletion of files (I:N, A:N), but the exposed information can enable further attacks.







