Atomic Edge analysis of CVE-2026-110516 (metadata-based): The All in One Addons For WPBakery Page Builder plugin for WordPress (slug: all-in-one-visual-composer-addons) is vulnerable to Local File Inclusion (LFI) in versions up to and including 1.2. An authenticated attacker with Contributor-level access or higher can include and execute arbitrary files on the server. The CVSS score is 7.5 (High) with vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. No patched version is available. Atomic Edge analysis is based solely on CVE metadata and WordPress plugin conventions; no source code diff was available for review.
Root Cause: The vulnerability is classified as CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program. This indicates that a user-supplied parameter is used directly in a PHP include or require statement without proper validation, sanitization, or restriction to a whitelist of allowed files. Based on the plugin’s name and common patterns, the vulnerable code likely resides in an AJAX handler or a shortcode/block rendering function that accepts a file path parameter for template or asset inclusion. The plugin fails to validate that the requested file is within the plugin directory or that it has an allowed extension (e.g., .php). Atomic Edge research infers that the plugin may use a parameter such as ‘template’, ‘file’, ‘path’, or ‘view’ to specify a file, and does not properly sanitize this input. This is reconstructed from the CWE, which explicitly points to filename control issues in include/require statements.
Exploitation: An authenticated attacker with Contributor-level access can send a crafted request to a vulnerable AJAX action. The attack vector is network-based (AV:N), requires low privileges (PR:L), and no user interaction (UI:N). The attacker would likely target an AJAX endpoint such as /wp-admin/admin-ajax.php with an action parameter corresponding to the vulnerable functionality. For example: action=vc_addons_include&template=../../../../wp-config.php. The attacker can then include arbitrary PHP files. If the plugin also allows uploading files with safe extensions (e.g., images) that contain PHP code, the attacker can include those files to achieve code execution. The CVSS vector indicates high confidentiality, integrity, and availability impact (C:H/I:H/A:H), confirming that successful exploitation leads to full server compromise. No specific action name is provided in the metadata; Atomic Edge analysis infers likely action names based on typical plugin naming patterns.
Remediation: The fix requires proper validation and sanitization of any user-supplied file paths before using them in include/require statements. The plugin should implement a whitelist of allowed files or restrict inclusions to a specific directory using realpath() and directory traversal checks. Additionally, capability checks and nonce verification should be enforced for any AJAX handlers. Since no patched version exists, the only mitigation is to disable or remove the plugin until a fix is available.
Impact: Successful exploitation allows an attacker with Contributor-level access to include and execute arbitrary PHP files. This can lead to complete server compromise, including remote code execution, access to sensitive data (e.g., wp-config.php, database credentials), and full control over the WordPress site. The CVSS score of 7.5 reflects the high impact on confidentiality, integrity, and availability.







