CVE-2022-4309

Subscribe2 <= 10.37 - Cross-Site Request Forgery

2022-12-22 00:00
WPScanTeam

Strategic Overview

Status
Patched in 10.38
Affected Plugin
Subscribe2 – Form, Email Subscribers & Newsletters
Affected Version
<= 10.37
CVSS
7.1High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-4309
View all Subscribe2 – Form, Email Subscribers & Newsletters vulnerabilities

At a glance

CVE-2022-4309 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Subscribe2 WordPress plugin, affecting versions <= 10.37. It carries a CVSS score of 7.1 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 10.38; sites on affected versions should update now. Disclosed December 2022, reported by WPScanTeam.

Vulnerability Overview

The Subscribe2 plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 10.37. This is due to missing or incorrect nonce validation on the process_bulk_action function. This makes it possible for unauthenticated attackers to delete users, 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 integrity.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Subscribe2 <= 10.37 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 Subscribe2 the fix is 10.38: builds <= 10.37 are affected, anything from 10.38 onward is not.

Remediation

Update to version 10.38, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4309https://www.wordfence.com/threat-intel/vulnerabilities/id/0e43d6fc-28f1-4208-a529-f264304fe8aahttps://nvd.nist.gov/vuln/detail/CVE-2022-4309

Related records

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