CVE-2023-6788

Metform Elementor Contact Form Builder <= 3.8.1 - Cross-Site Request Forgery

2024-01-08 00:00
Lucio Sá

Strategic Overview

Status
Patched in 3.8.2
Affected Plugin
MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor
Affected Version
<= 3.8.1
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-6788
View all MetForm – Contact Form, Survey, Quiz, Conditional Forms, Form Templates & Custom Form Builder for Elementor vulnerabilities

At a glance

CVE-2023-6788 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MetForm WordPress plugin, affecting versions <= 3.8.1. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.8.2; sites on affected versions should update now. Disclosed January 2024, reported by Lucio Sá.

Vulnerability Overview

The Metform Elementor Contact Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.8.1. This is due to missing or incorrect nonce validation on the contents function. This makes it possible for unauthenticated attackers to update the options "mf_hubsopt_token", "mf_hubsopt_refresh_token", "mf_hubsopt_token_type", and "mf_hubsopt_expires_in" via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. This would allow an attacker to connect their own Hubspot account to a victim site's metform to obtain leads and contacts.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

MetForm <= 3.8.1 carries this weakness at mf_hubsopt_token, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For MetForm the fix is 3.8.2: builds <= 3.8.1 are affected, anything from 3.8.2 onward is not.

Remediation

Update to version 3.8.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to MetForm: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MetForm 3.8.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6788https://www.wordfence.com/threat-intel/vulnerabilities/id/30fd2425-ee48-4777-91c1-03906d63793ahttps://nvd.nist.gov/vuln/detail/CVE-2023-6788

Related records

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