CVE-2021-4417

Forminator – Contact Form, Payment Form & Custom Form Builder <= 1.13.4 - Cross-Site Request Forgery Bypass

2021-03-01 00:00
Jerome Bruandet

Strategic Overview

Status
Patched in 1.13.5
Affected Plugin
Forminator Forms – Contact Form, Payment Form & Custom Form Builder
Affected Version
< 1.13.5
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-4417
View all Forminator Forms – Contact Form, Payment Form & Custom Form Builder vulnerabilities

At a glance

CVE-2021-4417 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Forminator Forms WordPress plugin, affecting versions < 1.13.5. 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 1.13.5; sites on affected versions should update now. Disclosed March 2021, reported by Jerome Bruandet.

Vulnerability Overview

The Forminator – Contact Form, Payment Form & Custom Form Builder plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.13.4. This is due to missing or incorrect nonce validation on the listen_for_saving_export_schedule() function. This makes it possible for unauthenticated attackers to export form submissions via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

Forminator Forms < 1.13.5 carries this weakness at listen_for_saving_export_schedule(), 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 Forminator Forms the fix is 1.13.5: builds < 1.13.5 are affected, anything from 1.13.5 onward is not.

Remediation

Update to version 1.13.5, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-4417https://www.wordfence.com/threat-intel/vulnerabilities/id/cdee0cd8-b83b-4436-aebe-533f5af03ef1https://nvd.nist.gov/vuln/detail/CVE-2021-4417

Related records

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