WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS missing authorization lets authors send arbitrary SMS
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
The WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS plugin for WordPress has a missing authorization flaw. A logged-in user with author-level access or higher can exploit it remotely over the network to send arbitrary SMS messages to any phone number, from the site's trusted sender ID. This can add per-message gateway charges for the site owner and enable SMS spam or phishing campaigns.
Written by a model
Original description
The WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 7.2.14. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with author-level access and above, to send arbitrary SMS messages to attacker-chosen phone numbers from the site's trusted sender ID, incurring per-message gateway charges to the site owner and enabling SMS spam or phishing campaigns.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-131577 (WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS <= 7.2.14 - Missing Authorization to Authenticated (Author+)…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-131577 (entry last updated 2026-11-21):
Affected:
- veronalabs WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS: through 7.2.14
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131577 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131577 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/297fa481-257c-4c45-8d0a-233770e12b02?source=cve
- https://plugins.trac.wordpress.org/browser/wp-sms/tags/7.2.14/includes/class-wpsms-notifications.php#L318
- https://plugins.trac.wordpress.org/browser/wp-sms/tags/7.2.14/includes/class-wpsms-notifications.php#L289
- https://plugins.trac.wordpress.org/browser/wp-sms/tags/7.2.14/includes/class-wpsms-notifications.php#L344
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3812959%40themify-builder&new=3812959%40themify-builder
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-131577
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131577"}.Affected versions
- veronalabs WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMSthrough 7.2.14
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 7
Questions about CVE-2026-131577
Is CVE-2026-131577 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
Which versions are affected by CVE-2026-131577?
WSMS (formerly WP SMS): SMS Notifications, OTP Login and WooCommerce SMS: through 7.2.14.
Source: cve.now feed data
Related
- CVE-2026-54818WordPress Slimstat Analytics plugin <= 5.4.11 - SQL Injection vulnerability
- CVE-2026-28136WordPress WP SMS plugin <= 6.9.12 - SQL Injection vulnerability
- CVE-2026-15780WP Statistics <= 14.16.8 - Unauthenticated Stored Cross-Site Scripting via 'utm_campaign' Parameter
- CVE-2026-7634SlimStat Analytics <= 5.4.11 - Unauthenticated Stored Cross-Site Scripting via User-Agent Header
- CVE-2026-5231WP Statistics <= 14.16.4 - Unauthenticated Stored Cross-Site Scripting via 'utm_source' Parameter
- CVE-2026-1238SlimStat Analytics <= 5.3.5 - Unauthenticated Stored Cross-Site Scripting via 'fh'
No corrections so far. Something wrong on this page? Report an error.