Multiline files upload for contact form 7 <= 2.8.1 - Missing Authorization to Authenticated (Subscriber+) Plugin Deactivation
Strategic Overview
- Status
- Patched in 2.9
- Affected Plugin
- MultiLine Files for Contact Form 7
- Affected Version
<= 2.8.1- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2024-9891
At a glance
CVE-2024-9891 is a medium-severity Missing Authorization vulnerability in the MultiLine Files for Contact Form 7 WordPress plugin, affecting versions <= 2.8.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 2.9; sites on affected versions should update now. Disclosed October 2024, reported by Tieu Pham Trong Nhan.
Vulnerability Overview
The Multiline files upload for contact form 7 plugin for WordPress is vulnerable to unauthorized plugin deactivation due to a missing capability check on the mfcf7_zl_custom_handle_deactivation_plugin_form_submission() function in all versions up to, and including, 2.8.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to deactivate the plugin and send a custom reason from the site.
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-862: Missing Authorization
MultiLine Files for Contact Form 7 <= 2.8.1 carries this weakness at mfcf7_zl_custom_handle_deactivation_plugin_form_submission(), and reaching it takes an account at Subscriber level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For MultiLine Files for Contact Form 7 the fix is 2.9: builds <= 2.8.1 are affected, anything from 2.9 onward is not.
Remediation
Update to version 2.9, 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: MultiLine Files for Contact Form 7 2.9 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C