CVE-2022-33201

MailerLite – Signup forms (official) <= 1.5.7 - Cross-Site Request Forgery

2022-08-01 00:00
Muhammad Daffa

Strategic Overview

Status
Patched in 1.5.8
Affected Plugin
MailerLite – Signup forms (official)
Affected Version
<= 1.5.7
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-33201
View all MailerLite – Signup forms (official) vulnerabilities

At a glance

CVE-2022-33201 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the MailerLite WordPress plugin, affecting versions <= 1.5.7. 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 1.5.8; sites on affected versions should update now. Disclosed August 2022, reported by Muhammad Daffa.

Vulnerability Overview

The MailerLite plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 1.5.7. This is due to missing or incorrect nonce validation several functions used to change plugin settings. This makes it possible for unauthenticated attackers to trigger setting updates via 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 MailerLite <= 1.5.7 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 MailerLite the fix is 1.5.8: builds <= 1.5.7 are affected, anything from 1.5.8 onward is not.

Remediation

Update to version 1.5.8, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-33201https://www.wordfence.com/threat-intel/vulnerabilities/id/156b955d-e978-4ff5-ab56-35af257b3199https://nvd.nist.gov/vuln/detail/CVE-2022-33201

Related records

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