WordPress security changelog
MEDIUM CVE-2026-15673 Deferred

SMS Alert stores administrator input that later reaches a cron SQL query

SMS Alert through 3.9.7 saves Administrator-controlled checkout_payment_plans and order_status settings through smsalert_Setting_Options::save() or saveSettings() and update_option(). When the cod_to_prepaid_cart_notification_sendsms_hook cron event later runs SA_CodTOPrepaid::sendSms(), those stored values are concatenated into a posts and postmeta SELECT query. An Administrator can therefore plant a second-order SQL-injection payload that executes asynchronously and can expose database data. Version 3.9.8 parameterizes the cron query with $wpdb->prepare().

CVE / CNA score 4.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery
Plugin slug
sms-alert
Affected
<= 3.9.7
Safe version
3.9.8
Published
Jul 28, 2026
Weakness
CWE-89 — Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

This CVE was published Jul 28, 2026 and is one of 15 known issues for this plugin.

What to do

Update, patch or deactivate.

Update SMS Alert to 3.9.8 or later. Review the COD-to-prepaid payment-plan and order-status settings, then replace any unexpected values before allowing the notification cron to run.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery plugin for WordPress is vulnerable to generic SQL Injection via 'checkout_payment_plans' and 'order_status' Settings in all versions up to, and including, 3.9.7 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with administrator-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This is a second-order SQL injection: the malicious payload is stored in the 'checkout_payment_plans' and 'order_status' settings via update_option() and executed later when the cod_to_prepaid_cart_notification_sendsms_hook WP-Cron event fires SA_CodTOPrepaid::sendSms().

CVE / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

References

Primary and upstream sources