Live Preview for Contact Form 7 <= 1.2.0 - Missing Authorization via update_option
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Live Preview for Contact Form 7
- Affected Version
<= 1.2.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2023-47830
At a glance
CVE-2023-47830 is a medium-severity Missing Authorization vulnerability in the Live Preview for Contact Form 7 WordPress plugin, affecting versions <= 1.2.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed November 2023, reported by thiennv.
Vulnerability Overview
The Live Preview for Contact Form 7 plugin for WordPress is vulnerable to unauthorized plugin option update due to a missing capability check on the update_option function in versions up to, and including, 1.2.0. This makes it possible for authenticated attackers, with subscriber access or higher, to update the plugin's options.
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
Reaching this weakness in Live Preview for Contact Form 7 <= 1.2.0 takes a caller who can reach the endpoint. 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. No fixed build of this plugin is recorded for Live Preview for Contact Form 7 yet, so installs running <= 1.2.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C