CVE-2023-47686

Arigato Autoresponder and Newsletter <= 2.7.2.2 - Cross-Site Request Forgery

2023-11-09 00:00
Nguyen Xuan Chien

Strategic Overview

Status
Patched in 2.7.2.3
Affected Plugin
Arigato Autoresponder and Newsletter
Affected Version
<= 2.7.2.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-47686
View all Arigato Autoresponder and Newsletter vulnerabilities

At a glance

CVE-2023-47686 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Arigato Autoresponder and Newsletter WordPress plugin, affecting versions <= 2.7.2.2. 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 2.7.2.3; sites on affected versions should update now. Disclosed November 2023, reported by Nguyen Xuan Chien.

Vulnerability Overview

The Arigato Autoresponder and Newsletter plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.7.2.2. This is due to missing or incorrect nonce validation on the bft_log() function. This makes it possible for unauthenticated attackers to trigger the view of all raw email logs via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. We do not consider this to be a real security issue as it appears to be a "view-only" CSRF.

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)

Arigato Autoresponder and Newsletter <= 2.7.2.2 carries this weakness at view-only, and reaching it 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 Arigato Autoresponder and Newsletter the fix is 2.7.2.3: builds <= 2.7.2.2 are affected, anything from 2.7.2.3 onward is not.

Remediation

Update to version 2.7.2.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-47686https://www.wordfence.com/threat-intel/vulnerabilities/id/1bf798b5-2a5c-42d9-a4b3-d3ed056e1fdbhttps://nvd.nist.gov/vuln/detail/CVE-2023-47686

Related records

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