# CVE-2024-13553: SMS Alert Order Notifications – WooCommerce <= 3.7.9 - Unauthenticated Account Takeover/Privilege Escalation

> Unauthenticated attackers can spoof the Host header to bypass OTP authentication and take over any user account, including administrators.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2qjj-4522-pjgp

## What is CVE-2024-13553?

CVE-2024-13553 is a critical authentication bypass vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SMS Alert Order Notifications – WooCommerce plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 3.7.9. This is due to the plugin using the Host header to determine if the plugin is in a playground environment. This makes it possible for unauthenticated attackers to spoof the Host header to make the OTP code "1234" and authenticate as any user, including administrators.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Cozyvision Sms Alert Order Notifications.

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

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

## Is CVE-2024-13553 being exploited?

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

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

- [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)
- [CVE-2025-26984](https://insights.sbomify.com/CVE-2025-26984/): Cross-site scripting in SMS Alert Order Notifications (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13553 and fix it if it is affected.

What it is: CVE-2024-13553 is a critical authentication bypass vulnerability in cozyvision1 SMS Alert – SMS & OTP for WooCommerce, Order Notifications & Abandoned Cart Recovery, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13553 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-13553/ (Markdown: https://insights.sbomify.com/CVE-2024-13553/index.md)
```

## Sources

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

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