# CVE-2024-1489: SMS Alert Order Notifications – WooCommerce <= 3.6.9 - Cross-Site Request Forgery

> Unauthenticated attackers can trick administrators into deleting pages and posts via forged requests in the SMS Alert Order Notifications plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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:** 13 Mar 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-fq3v-wrf2-mrf5

## What is CVE-2024-1489?

CVE-2024-1489 is a medium-severity vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 13 Mar 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 SMS Alert Order Notifications – WooCommerce plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.6.9. This is due to missing or incorrect nonce validation on the processBulkAction function. This makes it possible for unauthenticated attackers to delete pages and posts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2024-1489?

It affects 1 product.


Products: Cozyvision Sms Alert Order Notifications.

## How do I fix CVE-2024-1489?

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

## Is CVE-2024-1489 being exploited?

There is no known exploitation of CVE-2024-1489 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-2024-1489 and fix it if it is affected.

What it is: CVE-2024-1489 is a medium-severity vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 13 Mar 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-2024-1489 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-2024-1489/ (Markdown: https://insights.sbomify.com/CVE-2024-1489/index.md)
```

## Sources

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

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