# CVE-2025-3878: Cross-site scripting in SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery

> Authenticated attackers can inject arbitrary web scripts via the sa_verify shortcode, executing them when other users view the page.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-v7fg-84w6-2g4w

## What is CVE-2025-3878?

CVE-2025-3878 is a medium-severity cross-site scripting vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 10 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SMS Alert Order Notifications – WooCommerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's sa_verify shortcode in all versions up to, and including, 3.8.1 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2025-3878?

It affects 1 product.


Products: Cozyvision Sms Alert Order Notifications.

## How do I fix CVE-2025-3878?

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

## Is CVE-2025-3878 being exploited?

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

## Other vulnerabilities in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery

- [CVE-2024-13553](https://insights.sbomify.com/CVE-2024-13553/): SMS Alert Order Notifications – WooCommerce <= 3.7.9 - Unauthenticated Account Takeover/Privilege Escalation (critical 9.8)
- [CVE-2025-47682](https://insights.sbomify.com/CVE-2025-47682/): WordPress SMS Alert Order Notifications – WooCommerce plugin <= 3.8.1 - SQL Injection Vulnerability (critical 9.3)
- [CVE-2025-26988](https://insights.sbomify.com/CVE-2025-26988/): WordPress SMS Alert Order Notifications – WooCommerce plugin <= 3.7.8 - SQL Injection vulnerability (critical 9.3)
- [CVE-2025-3876](https://insights.sbomify.com/CVE-2025-3876/): Privilege escalation in SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery (high 8.8)
- [CVE-2024-11725](https://insights.sbomify.com/CVE-2024-11725/): Missing authorization in SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3878 and fix it if it is affected.

What it is: CVE-2025-3878 is a medium-severity cross-site scripting vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 10 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3878 in the wild and no public exploit code.

Affected product: cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery. 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-2025-3878/ (Markdown: https://insights.sbomify.com/CVE-2025-3878/index.md)
```

## Sources

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

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