CVE-2024-5053

Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder <= 5.1.18 - Missing Authorization to Authenticated (Subscriber+) Mailchimp Integration Modification

Strategic Overview

At a glance

CVE-2024-5053 is a medium-severity Improper Authorization vulnerability in the Fluent Forms WordPress plugin, affecting versions <= 5.1.18. It carries a CVSS score of 4.2 (reachable over the network). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 5.1.19; sites on affected versions should update now. Disclosed August 2024, reported by Tobias Weißhaar (kun_19).

Vulnerability Overview

The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder plugin for WordPress is vulnerable to unauthorized Malichimp API key update due to an insufficient capability check on the verifyRequest function in all versions up to, and including, 5.1.18. This makes it possible for Form Managers with a Subscriber-level access and above to modify the Mailchimp API key used for integration. At the same time, missing Mailchimp API key validation allows the redirect of the integration requests to the attacker-controlled server.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no interaction from a victim user.

CWE-285: Improper Authorization

Reaching this weakness in Fluent Forms <= 5.1.18 takes an account at Subscriber level or above. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Fluent Forms the fix is 5.1.19: builds <= 5.1.18 are affected, anything from 5.1.19 onward is not.

Remediation

Update to version 5.1.19, 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: Fluent Forms 5.1.19 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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