WP Maintenance Mode & Coming Soon <= 2.4.4 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 2.4.5
- Affected Version
<= 2.4.4- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-1576
At a glance
CVE-2022-1576 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the LightStart WordPress plugin, affecting versions <= 2.4.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.4.5; sites on affected versions should update now. Disclosed June 2022, reported by Daniel Ruf.
Vulnerability Overview
The WP Maintenance Mode & Coming Soon plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.4.4. This is due to missing nonce validation on the reset_plugin_settings, subscribers_empty_list, dismiss_notices, subscribers_export, add_subscriber, & send_contact functions. This makes it possible for unauthenticated attackers to perform a variety of actions such as emptying the subscribers list and resetting the plugin's settings 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in LightStart <= 2.4.4 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 LightStart the fix is 2.4.5: builds <= 2.4.4 are affected, anything from 2.4.5 onward is not.
Remediation
Update to version 2.4.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to LightStart: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: LightStart 2.4.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in LightStart – Maintenance Mode, Coming Soon and Landing Page Builder
- 9.1CVE-2018-20156: WP Maintenance Mode <= 2.0.6 Remote Code Execution
CVE-2018-20156 - 5.4CVE-2018-20155: WP Maintenance Mode <= 2.0.6 Missing Authorization
CVE-2018-20155 - 5.3CVE-2024-1047: ThemeIsle SDK <= Various Versions Missing Authorization
CVE-2024-1047 - 4.3CVE-2023-7019: LightStart Missing Authorization
CVE-2023-7019 - 4.3CVE-2018-20154: WP Maintenance Mode <= 2.0.6 Information Disclosure
CVE-2018-20154
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C