CVE-2023-0691

Metform Elementor Contact Form Builder <= 3.3.1 - Authenticated (Subscriber+) Information Disclosure via mf_last_name shortcode

2023-06-08 00:00
Ram

Strategic Overview

Status
Patched in 3.3.2
Affected Plugin
MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor
Affected Version
<= 3.3.1
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-0691
View all MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor vulnerabilities

At a glance

CVE-2023-0691 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MetForm WordPress plugin, affecting versions <= 3.3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.3.2; sites on affected versions should update now. Disclosed June 2023, reported by Ram.

Vulnerability Overview

The Metform Elementor Contact Form Builder for WordPress is vulnerable to Information Disclosure via the 'mf_last_name' shortcode in versions up to, and including, 3.3.1. This allows authenticated attackers, with subscriber-level capabilities or above to obtain sensitive information about arbitrary form submissions, specifically the submitter's last name.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

MetForm <= 3.3.1 carries this weakness at mf_last_name, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For MetForm the fix is 3.3.2: builds <= 3.3.1 are affected, anything from 3.3.2 onward is not.

Remediation

Update to version 3.3.2, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: MetForm 3.3.2 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-0691https://www.wordfence.com/threat-intel/vulnerabilities/id/8fc4b815-dc05-4270-bf7a-3b01622739d7https://nvd.nist.gov/vuln/detail/CVE-2023-0691

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C