CVE-2023-6980

WP SMS <= 6.5 - Cross-Site Request Forgery to Subscriber Deletion

2024-01-02 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 6.5.1
Affected Plugin
WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce
Affected Version
<= 6.5
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-6980
View all WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce vulnerabilities

At a glance

CVE-2023-6980 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WSMS (formerly WP SMS) WordPress plugin, affecting versions <= 6.5. 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 6.5.1; sites on affected versions should update now. Disclosed January 2024, reported by Krzysztof Zając.

Vulnerability Overview

The WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 6.5. This is due to missing or incorrect nonce validation on the 'delete' action of the wp-sms-subscribers page. This makes it possible for unauthenticated attackers to delete subscribers 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)

WSMS (formerly WP SMS) <= 6.5 carries this weakness at delete, 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 WSMS (formerly WP SMS) the fix is 6.5.1: builds <= 6.5 are affected, anything from 6.5.1 onward is not.

Remediation

Update to version 6.5.1, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-6980https://www.wordfence.com/threat-intel/vulnerabilities/id/94ad6b51-ff8d-48d5-9a70-1781d13990a5https://nvd.nist.gov/vuln/detail/CVE-2023-6980

Related records

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