CVE-2023-3407

Subscribe2 <= 10.40 - Cross-Site Request Forgery

2023-06-26 00:00

Strategic Overview

Status: Patched in 10.41
Affected Plugin: Subscribe2 – Form, Email Subscribers & Newsletters
Affected Version: <= 10.40
CVSS: 4.3Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2023-3407

View all Subscribe2 – Form, Email Subscribers & Newsletters vulnerabilities

At a glance

CVE-2023-3407 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Subscribe2 WordPress plugin, affecting versions <= 10.40. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.41; sites on affected versions should update now. Disclosed June 2023, reported by Marco Wotschka.

Vulnerability Overview

The Subscribe2 plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 10.40. This is due to missing or incorrect nonce validation when sending test emails. This makes it possible for unauthenticated attackers to send test emails with custom content to users on sites running a vulnerable version of this plugin 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.

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

Reaching this weakness in Subscribe2 <= 10.40 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.41: builds <= 10.40 are affected, anything from 10.41 onward is not.

Remediation

Update to version 10.41, 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.41 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-3407 https://www.wordfence.com/threat-intel/vulnerabilities/id/92b4d800-2895-4f7b-8b3b-ee6df75a7908 https://nvd.nist.gov/vuln/detail/CVE-2023-3407

Related records

Same weakness class

Other vulnerabilities in Subscribe2 – Form, Email Subscribers & Newsletters

CVSS Vector

4.3

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeUnchanged
ConfidentialityNone
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/