CVE-2023-32504

Wise Chat <= 3.1.3 - Cross-Site Request Forgery

2023-05-09 00:00
Justiice

Strategic Overview

Status
Patched in 3.1.4
Affected Plugin
Wise Chat
Affected Version
<= 3.1.3
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-32504
View all Wise Chat vulnerabilities

At a glance

CVE-2023-32504 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Wise Chat WordPress plugin, affecting versions <= 3.1.3. 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 3.1.4; sites on affected versions should update now. Disclosed May 2023, reported by Justiice.

Vulnerability Overview

The Wise Chat plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.1.3. This is due to missing nonce validation on several functions such as resetAnonymousCounterAction, resetSettingsAction, deleteAllUsersAndMessagesAction, deleteBanAction, addBanAction, clearChannelAction, deleteChannelAction, backupChannelAction, and more. This makes it possible for unauthenticated attackers to control the plugin's setttings 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 Wise Chat <= 3.1.3 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 Wise Chat the fix is 3.1.4: builds <= 3.1.3 are affected, anything from 3.1.4 onward is not.

Remediation

Update to version 3.1.4, or a newer patched version

How does WordSec protect against this?

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