CVE-2022-29414

Subscribe To Comments Reloaded <= 211130 - Cross-Site Request Forgery

2022-04-29 12:07
R3N0

Strategic Overview

Status
Patched in 220502
Affected Version
<= 211130
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-29414
View all Subscribe To Comments Reloaded vulnerabilities

At a glance

CVE-2022-29414 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Subscribe To Comments Reloaded WordPress plugin, affecting versions <= 211130. 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 220502; sites on affected versions should update now. Disclosed April 2022, reported by R3N0.

Vulnerability Overview

Multiple (13x) Cross-Site Request Forgery (CSRF) vulnerabilities in WPKube's Subscribe To Comments Reloaded plugin <= 211130 on WordPress allows attackers to clean up Log archive, download system info file, plugin system settings, plugin options settings, generate a new key, reset all options, change notifications settings, management page settings, comment form settings, manage subscriptions > mass update settings, manage subscriptions > add a new subscription, update subscription, delete Subscription.

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 Subscribe To Comments Reloaded <= 211130 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 Subscribe To Comments Reloaded the fix is 220502: builds <= 211130 are affected, anything from 220502 onward is not.

Remediation

Update to version 220502, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Subscribe To Comments Reloaded: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Subscribe To Comments Reloaded 220502 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