Multilang Contact Form Security & Risk Analysis

wordpress.org/plugins/multilang-contact-form

Multilang Contact Form is a very simple and easy contact form compatible with qtranslate. It can be

60 active installs v1.5 PHP + WP 2.5+ Updated Nov 14, 2012
contactmultilangqtranslatedtemplate
42
D · High Risk
CVEs total2
Unpatched2
Last CVESep 26, 2025
Safety Verdict

Is Multilang Contact Form Safe to Use in 2026?

High Risk

Score 42/100

Multilang Contact Form carries significant security risk with 2 known CVEs, 2 still unpatched. Consider switching to a maintained alternative.

2 known CVEs 2 unpatched Last CVE: Sep 26, 2025Updated 13yr ago
Risk Assessment

The "multilang-contact-form" plugin, version 1.5, exhibits a mixed security posture. While it demonstrates good practices by utilizing prepared statements for all SQL queries and having a minimal attack surface with no unprotected entry points, significant concerns arise from its output escaping and vulnerability history. The static analysis reveals that 100% of output is not properly escaped, indicating a high risk of Cross-Site Scripting (XSS) vulnerabilities. This is further corroborated by the vulnerability history, which shows two medium-severity CVEs, specifically mentioning Cross-Site Request Forgery (CSRF) and Cross-site Scripting (XSS). The presence of unpatched vulnerabilities, particularly those related to XSS, is a serious red flag. The taint analysis also highlights one flow with an unsanitized path, although it was not classified as critical or high, it still warrants attention in conjunction with the unescaped output.

In conclusion, despite some commendable security implementations like prepared SQL statements, the plugin's failure to properly escape output and its history of unpatched XSS and CSRF vulnerabilities pose a considerable risk. The lack of proper output escaping makes it susceptible to XSS attacks, which can be leveraged to exploit other vulnerabilities or compromise user sessions. Users of this plugin should be aware of these risks and prioritize updating to a version that addresses these persistent security flaws.

Key Concerns

  • Unpatched CVEs (2 medium)
  • No proper output escaping
  • Taint analysis: 1 unsanitized path flow
  • No nonce checks
Vulnerabilities
2 published

Multilang Contact Form Security Vulnerabilities

CVEs by Year

2 CVEs in 2025 · unpatched
2025
Patched Has unpatched

Severity Breakdown

Medium
2

2 total CVEs

CVE-2025-62896medium · 4.3Cross-Site Request Forgery (CSRF)

Multilang Contact Form <= 1.5 - Cross-Site Request Forgery

Sep 26, 2025Unpatched
CVE-2025-22795medium · 6.1Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Multilang Contact Form <= 1.5 - Reflected Cross-Site Scripting

Jan 13, 2025Unpatched
Code Analysis
Analyzed Mar 16, 2026

Multilang Contact Form Code Analysis

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

Output Escaping

0% escaped26 total outputs
Data Flows · Security
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<ml-contactform-options> (ml-contactform-options.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface

Multilang Contact Form Attack Surface

Entry Points1
Unprotected0

Shortcodes 1

[contact_form] ml-contactform.php:325
WordPress Hooks 1
actionadmin_menuml-contactform.php:324
Maintenance & Trust

Multilang Contact Form Maintenance & Trust

Maintenance Signals

WordPress version tested3.4.2
Last updatedNov 14, 2012
PHP min version
Downloads12K

Community Trust

Rating0/100
Number of ratings0
Active installs60
Developer Profile

Multilang Contact Form Developer Profile

digitaldonkey

3 plugins · 80 total installs

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

How We Detect Multilang Contact Form

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

Asset Fingerprints

Asset Paths
/wp-content/plugins/multilang-contact-form/recaptchalib.php
Version Parameters
multilang-contact-form/style.css?ver=multilang-contact-form/mlcf.js?ver=

HTML / DOM Fingerprints

CSS Classes
contactrightcontacterrorcontactalert
Data Attributes
id="mlcf_name"id="mlcf_email"id="mlcf_subject"id="mlcf_www"id="mlcf_message"name="mlcf_name"+7 more
JS Globals
var RecaptchaOptionsmlcf_strings
Shortcode Output
[contact_form]
FAQ

Frequently Asked Questions about Multilang Contact Form