WP Bakery Multilanguage Security & Risk Analysis

wordpress.org/plugins/multilanguage-add-on-for-visual-composer

This is an add-on plugin for WPBakery Visual Composer that adds multilanguage support and functionality. Version 2.0 now also has automatic translatio …

200 active installs v2.1.2 PHP + WP + Updated May 7, 2022
multi-languagemultilanguagetranslatetranslationvisual-composer
85
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is WP Bakery Multilanguage Safe to Use in 2026?

Generally Safe

Score 85/100

WP Bakery Multilanguage has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs Updated 3yr ago
Risk Assessment

The "multilanguage-add-on-for-visual-composer" plugin v2.1.2 exhibits a generally strong security posture based on the provided static analysis. The absence of any identified dangerous functions, SQL queries that are not prepared, file operations, external HTTP requests, and a clean taint analysis are all positive indicators. Furthermore, the plugin has no known historical vulnerabilities, which suggests a history of responsible development and maintenance. The large number of output escapings (54 total) is a good sign, though the percentage of properly escaped outputs (30%) is a notable concern.

Despite the positive indicators, the 30% proper escaping rate for output is a significant weakness. This suggests that a substantial portion of user-generated or dynamic content displayed by the plugin may not be adequately sanitized, leaving it vulnerable to cross-site scripting (XSS) attacks. While the static analysis did not directly flag any XSS vulnerabilities, this low escaping rate represents a clear risk. The lack of any capability checks, nonce checks, or apparent authentication on entry points (even though the attack surface is zero) could also be a latent concern if any entry points were to be introduced in future versions or if the static analysis was incomplete.

In conclusion, the plugin's core code appears robust against many common server-side vulnerabilities. However, the inadequate output escaping is a significant and actionable concern that requires immediate attention to prevent potential client-side attacks. The lack of historical vulnerabilities is a strength, but the present issue with output escaping highlights a weakness that needs to be addressed.

Key Concerns

  • Low percentage of properly escaped output
Vulnerabilities
None known

WP Bakery Multilanguage Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 16, 2026

WP Bakery Multilanguage Code Analysis

Dangerous Functions
0
Raw SQL Queries
0
0 prepared
Unescaped Output
38
16 escaped
Nonce Checks
0
Capability Checks
0
File Operations
0
External Requests
0
Bundled Libraries
0

Output Escaping

30% escaped54 total outputs
Attack Surface

WP Bakery Multilanguage Attack Surface

Entry Points0
Unprotected0
WordPress Hooks 20
actionplugins_loadedincludes\class-visual-composer-multilanguage.php:139
actionadmin_enqueue_scriptsincludes\class-visual-composer-multilanguage.php:154
actionadmin_enqueue_scriptsincludes\class-visual-composer-multilanguage.php:155
actionadmin_menuincludes\class-visual-composer-multilanguage.php:157
actionadmin_initincludes\class-visual-composer-multilanguage.php:159
actionwp_enqueue_scriptsincludes\class-visual-composer-multilanguage.php:174
actionwp_enqueue_scriptsincludes\class-visual-composer-multilanguage.php:175
actionwp_loadedincludes\class-visual-composer-multilanguage.php:177
actionwp_footerincludes\class-visual-composer-multilanguage.php:178
actionwp_footerincludes\class-visual-composer-multilanguage.php:179
actionplugins_loadedtrunk\includes\class-visual-composer-multilanguage.php:139
actionadmin_enqueue_scriptstrunk\includes\class-visual-composer-multilanguage.php:154
actionadmin_enqueue_scriptstrunk\includes\class-visual-composer-multilanguage.php:155
actionadmin_menutrunk\includes\class-visual-composer-multilanguage.php:157
actionadmin_inittrunk\includes\class-visual-composer-multilanguage.php:159
actionwp_enqueue_scriptstrunk\includes\class-visual-composer-multilanguage.php:174
actionwp_enqueue_scriptstrunk\includes\class-visual-composer-multilanguage.php:175
actionwp_loadedtrunk\includes\class-visual-composer-multilanguage.php:177
actionwp_footertrunk\includes\class-visual-composer-multilanguage.php:178
actionwp_footertrunk\includes\class-visual-composer-multilanguage.php:179
Maintenance & Trust

WP Bakery Multilanguage Maintenance & Trust

Maintenance Signals

WordPress version tested6.0.11
Last updatedMay 7, 2022
PHP min version
Downloads28K

Community Trust

Rating0/100
Number of ratings0
Active installs200
Developer Profile

WP Bakery Multilanguage Developer Profile

allurewebsolutions

3 plugins · 4K total installs

84
trust score
Avg Security Score
85/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect WP Bakery Multilanguage

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/visual-composer-multilanguage/css/visual-composer-multilanguage-admin.css/wp-content/plugins/visual-composer-multilanguage/js/visual-composer-multilanguage-admin.js
Script Paths
/wp-content/plugins/visual-composer-multilanguage/js/visual-composer-multilanguage-admin.js
Version Parameters
visual-composer-multilanguage/css/visual-composer-multilanguage-admin.css?ver=visual-composer-multilanguage/js/visual-composer-multilanguage-admin.js?ver=

HTML / DOM Fingerprints

CSS Classes
visual-composer-multilanguage
FAQ

Frequently Asked Questions about WP Bakery Multilanguage