# CVE-2023-6981: WP SMS <= 6.5 - Authenticated (Admin+) SQL Injection to Reflected Cross-Site Scripting

> Authenticated attackers can exploit SQL injection in WP SMS plugin to extract database information and achieve reflected cross-site scripting.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Jan 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-q2g5-wh6f-x8q9

## What is CVE-2023-6981?

CVE-2023-6981 is a medium-severity SQL injection vulnerability in veronalabs WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-6981?

It affects 1 product.


Products: Veronalabs Wp Sms.

## How do I fix CVE-2023-6981?

No fix has been published for CVE-2023-6981 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-6981 being exploited?

There is no known exploitation of CVE-2023-6981 in the wild and no public exploit code.

## Other vulnerabilities in veronalabs WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce

- [CVE-2024-24881](https://insights.sbomify.com/CVE-2024-24881/): WordPress WP SMS Plugin <= 6.5.2 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2023-32742](https://insights.sbomify.com/CVE-2023-32742/): WordPress WP SMS Plugin <= 6.1.4 is vulnerable to Cross Site Scripting (XSS) (high 7.1)
- [CVE-2024-25920](https://insights.sbomify.com/CVE-2024-25920/): WordPress WP SMS plugin <= 6.3.4 - Cross Site Scripting (XSS) vulnerability (medium 6.5)
- [CVE-2024-34811](https://insights.sbomify.com/CVE-2024-34811/): WordPress WP SMS plugin <= 6.5.1 - Cross Site Scripting (XSS) vulnerability (medium 5.9)
- [CVE-2021-24561](https://insights.sbomify.com/CVE-2021-24561/): WP SMS < 5.4.13 - Authenticated Stored Cross-Site Scripting (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-6981 and fix it if it is affected.

What it is: CVE-2023-6981 is a medium-severity SQL injection vulnerability in veronalabs WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce, published on 3 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-6981 in the wild and no public exploit code.

Affected product: veronalabs WSMS (formerly WP SMS) – SMS & MMS Notifications with OTP and 2FA for WooCommerce. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-6981/ (Markdown: https://insights.sbomify.com/CVE-2023-6981/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-6981
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-6981
- OSV: https://osv.dev/vulnerability/CVE-2023-6981

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-6981/
Summaries are generated and may contain mistakes; the official description above is the record.