Is WSMS (formerly WP SMS) safe to use?

Laskyr does not give safety verdicts. No known unpatched vulnerabilities in the latest version (7.2.11). As of 2026-11-04. 14 issues are on record for older versions; version 7.2.2 or newer fixes all of them that state a fix. Keep WSMS (formerly WP SMS) on the latest version (7.2.11) and remove it if you do not use it.

Which versions of WSMS (formerly WP SMS) are vulnerable?

Known issues on record (newest first): Information disclosure (7.2.1 and older, fixed in 7.2.2); SQL injection (6.9.12 and older, fixed in 7.0); Cross-site scripting (XSS) (7.1 and older, fixed in 7.1.1); Missing authorization check (7.0.1 and older, fixed in 7.0.2); Missing authorization check (6.9.3 and older, fixed in 6.9.4); Stored cross-site scripting (XSS) (6.5.1 and older, fixed in 6.5.2). The full list with sources is on this page.

What is the latest version of WSMS (formerly WP SMS)?

7.2.11, according to wordpress.org (last updated 2026-11-02). It has 7,000+ active installs.

What should I do if my WSMS (formerly WP SMS) is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update wp-sms). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · wp-sms · data as of 2026-11-04

Is WSMS (formerly WP SMS) safe? Known vulnerabilities and latest version

Latest version: 7.2.11
Last updated: 2026-11-02
Active installs: 7,000+
Known issues on record: 14
Unpatched in latest: 0
Tested up to WP: 7.1.4 · PHP 7.4+

Send SMS notifications, OTP login and 2FA codes, and WooCommerce order SMS from WordPress through 260+ SMS gateways. — by VeronaLabs

What to do

Update to the latest version (7.2.11). Anything older than 7.2.2 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
If you cannot update right away, deactivate it until you can.
Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.

With WP-CLI: wp plugin get wp-sms --field=version shows what you run; wp plugin update wp-sms updates it.

Check your version

Known vulnerabilities

14 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 6.5 CVE-2026-40790 · published 2026-06-15

Information disclosure in WSMS (formerly WP SMS) (7.2.1 and older)

Affected: 7.2.1 and older
Fixed in: 7.2.2
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Subscriber Sensitive Data Exposure in WP SMS <= 7.2.1 versions.

NVD CVE-2026-40790 Patchstack advisory

high 7.6 CVE-2026-28136 · published 2026-02-26

SQL injection in WSMS (formerly WP SMS) (6.9.12 and older)

Affected: 6.9.12 and older
Fixed in: 7.0
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in VeronaLabs WP SMS wp-sms allows SQL Injection.This issue affects WP SMS: from n/a through <= 6.9.12.

NVD CVE-2026-28136 Patchstack advisory

medium 5.9 CVE-2026-25343 · published 2026-02-19

Cross-site scripting (XSS) in WSMS (formerly WP SMS) (7.1 and older)

Affected: 7.1 and older
Fixed in: 7.1.1
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VeronaLabs WP SMS wp-sms allows DOM-Based XSS.This issue affects WP SMS: from n/a through <= 7.1.

NVD CVE-2026-25343 Patchstack advisory

medium 5.4 CVE-2025-62006 · published 2025-10-22

Missing authorization check in WSMS (formerly WP SMS) (7.0.1 and older)

Affected: 7.0.1 and older
Fixed in: 7.0.2
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Missing Authorization vulnerability in VeronaLabs WP SMS wp-sms.This issue affects WP SMS: from n/a through <= 7.0.1.

NVD CVE-2025-62006 Patchstack advisory

critical 9.8 CVE-2024-43331 · published 2024-08-22

Missing authorization check in WSMS (formerly WP SMS) (6.9.3 and older)

Affected: 6.9.3 and older
Fixed in: 6.9.4
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Missing Authorization vulnerability in VeronaLabs WP SMS.This issue affects WP SMS: from n/a through 6.9.3.

NVD CVE-2024-43331 Patchstack advisory

medium 4.8 CVE-2024-34811 · published 2024-05-14

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5.1 and older)

Affected: 6.5.1 and older
Fixed in: 6.5.2
Access needed (per CVSS): Needs an admin-level account; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VeronaLabs WP SMS allows Stored XSS.This issue affects WP SMS: from n/a through 6.5.1.

NVD CVE-2024-34811 Patchstack advisory

high 8.8 CVE-2024-30454 · published 2024-03-29

Cross-site request forgery (CSRF) in WSMS (formerly WP SMS) (6.6.2 and older)

Affected: 6.6.2 and older
Fixed in: 6.6.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in VeronaLabs WP SMS.This issue affects WP SMS: from n/a through 6.6.2.

NVD CVE-2024-30454 Patchstack advisory

medium 5.4 CVE-2024-25920 · published 2024-03-27

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.3.4 and older)

Affected: 6.3.4 and older
Fixed in: 6.4
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VeronaLabs WP SMS allows Stored XSS.This issue affects WP SMS: from n/a through 6.3.4.

NVD CVE-2024-25920 Patchstack advisory

medium 6.1 CVE-2024-24881 · published 2024-02-08

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5.2 and older)

Affected: 6.5.2 and older
Fixed in: 6.5.3
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VeronaLabs WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc allows Reflected XSS.This issue affects WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc: from n/a through 6.5.2.

NVD CVE-2024-24881 Patchstack advisory

medium 4.3 CVE-2023-6980 · published 2024-01-03

Cross-site request forgery (CSRF) in WSMS (formerly WP SMS) (6.5 and older)

Affected: 6.5 and older
Fixed in: 6.5.1 *
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

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.

NVD CVE-2023-6980 Wordfence advisory Code change (fix)github.com

medium 4.9 CVE-2023-6981 · published 2024-01-03

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5 and older)

Affected: 6.5 and older
Fixed in: 6.5.1 *
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

The WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc plugin for WordPress is vulnerable to SQL Injection via the 'group_id' parameter in all versions up to, and including, 6.5 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 contributor-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 can leveraged to achieve Reflected Cross-site Scripting.

NVD CVE-2023-6981 Wordfence advisory Code change (fix)github.com

high 7.5 CVE-2023-27447 · published 2023-12-28

Information disclosure in WSMS (formerly WP SMS) (6.0.4 and older)

Affected: 6.0.4 and older
Fixed in: 6.0.4.1
Access needed (per CVSS): No login needed
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in VeronaLabs WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc.This issue affects WP SMS – Messaging & SMS Notification for WordPress, WooCommerce, GravityForms, etc: from n/a through 6.0.4.

NVD CVE-2023-27447 Patchstack advisory

medium 6.1 CVE-2023-32742 · published 2023-08-30

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.1.4 and older)

Affected: 6.1.4 and older
Fixed in: 6.1.5
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by NVD

Details from the advisory

Unauth. Reflected Cross-Site Scripting (XSS) vulnerability in VeronaLabs WP SMS plugin <= 6.1.4 versions.

NVD CVE-2023-32742 Patchstack advisory

medium 5.4 CVE-2021-24561 · published 2021-08-23

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (older than 5.4.13)

Affected: older than 5.4.13
Fixed in: 5.4.13
Access needed (per CVSS): Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
Range from: NVD analysis · score by NVD

Details from the advisory

The WP SMS WordPress plugin before 5.4.13 does not sanitise the "wp_group_name" parameter before outputting it back in the "Groups" page, leading to an Authenticated Stored Cross-Site Scripting issue

NVD CVE-2021-24561 WPScan advisory Code change (fix)

Recent activity

2026-11-02 — latest release on wordpress.org (7.2.11).
2026-06-15 — Information disclosure disclosed (CVE-2026-40790), fixed in 7.2.2.
2026-02-26 — SQL injection disclosed (CVE-2026-28136), fixed in 7.0.
2026-02-19 — Cross-site scripting (XSS) disclosed (CVE-2026-25343), fixed in 7.1.1.

Free. We check the CVE feeds every day and email you only when a new issue for WSMS (formerly WP SMS) (wp-sms) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site scripting (XSS) (7) · Sensitive data exposure (2) · Missing authorization (2) · Cross-site request forgery (CSRF) (2) · SQL injection (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/wp-sms (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/wp-sms"><img src="https://laskyr.com/plugins/wp-sms/badge.svg" alt="WSMS (formerly WP SMS) vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is WSMS (formerly WP SMS) safe? Known vulnerabilities and latest version

No known unpatched vulnerabilities in the latest version (7.2.11)

What to do

Check your version

Known vulnerabilities

Information disclosure in WSMS (formerly WP SMS) (7.2.1 and older)

SQL injection in WSMS (formerly WP SMS) (6.9.12 and older)

Cross-site scripting (XSS) in WSMS (formerly WP SMS) (7.1 and older)

Missing authorization check in WSMS (formerly WP SMS) (7.0.1 and older)

Missing authorization check in WSMS (formerly WP SMS) (6.9.3 and older)

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5.1 and older)

Cross-site request forgery (CSRF) in WSMS (formerly WP SMS) (6.6.2 and older)

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.3.4 and older)

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5.2 and older)

Cross-site request forgery (CSRF) in WSMS (formerly WP SMS) (6.5 and older)

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.5 and older)

Information disclosure in WSMS (formerly WP SMS) (6.0.4 and older)

Reflected cross-site scripting (XSS) in WSMS (formerly WP SMS) (6.1.4 and older)

Stored cross-site scripting (XSS) in WSMS (formerly WP SMS) (older than 5.4.13)

Recent activity

Get an email when WSMS (formerly WP SMS) has a new vulnerability

Browse vulnerabilities

Where this data comes from