CVE-2022-1603

Mail Subscribe List <= 2.1.3 - Cross-Site Request Forgery

2022-05-26 00:00
Daniel Ruf

Strategic Overview

Status
Patched in 2.1.4
Affected Plugin
Mail Subscribe List
Affected Version
< 2.1.4
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-1603
View all Mail Subscribe List vulnerabilities

At a glance

CVE-2022-1603 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Mail Subscribe List WordPress plugin, affecting versions < 2.1.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.1.4; sites on affected versions should update now. Disclosed May 2022, reported by Daniel Ruf.

Vulnerability Overview

The Mail Subscribe List WordPress plugin before 2.1.4 does not have CSRF check in place when deleting subscribed users, which could allow attackers to make a logged in admin perform such action and delete arbitrary users from the subscribed list

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 Mail Subscribe List < 2.1.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 Mail Subscribe List the fix is 2.1.4: builds < 2.1.4 are affected, anything from 2.1.4 onward is not.

Remediation

Update to version 2.1.4, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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