# CVE-2022-0199: Coming soon and Maintenance mode < 3.6.8 - Arbitrary Email Sending to Subscribed Users via CSRF

> Attackers can trick admins into sending arbitrary emails to subscribers via CSRF in the Coming soon and Maintenance mode 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:** 21 Feb 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4hmp-c47h-m87p

## What is CVE-2022-0199?

CVE-2022-0199 is a medium-severity vulnerability in Unknown Coming soon and Maintenance mode, published on 21 Feb 2022. 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 Coming soon and Maintenance mode WordPress plugin before 3.6.8 does not have CSRF check in its coming_soon_send_mail AJAX action, allowing attackers to make logged in admin to send arbitrary emails to all subscribed users via a CSRF attack

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

## Which versions are affected by CVE-2022-0199?

It affects 1 product.


Products: Wpdevart Coming Soon and Maintenance Mode.

## How do I fix CVE-2022-0199?

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

## Is CVE-2022-0199 being exploited?

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

## Other vulnerabilities in Unknown Coming soon and Maintenance mode

- [CVE-2021-24577](https://insights.sbomify.com/CVE-2021-24577/): Coming Soon and Maintenance Mode < 3.5.3 - Authenticated Stored XSS (medium 5.4)
- [CVE-2022-0164](https://insights.sbomify.com/CVE-2022-0164/): Coming soon and Maintenance mode < 3.6.7 - Subscriber+ Arbitrary Email Sending to Subscribed Users (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0199 and fix it if it is affected.

What it is: CVE-2022-0199 is a medium-severity vulnerability in Unknown Coming soon and Maintenance mode, published on 21 Feb 2022. 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-2022-0199 in the wild and no public exploit code.

Affected product: Unknown Coming soon and Maintenance mode. 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-2022-0199/ (Markdown: https://insights.sbomify.com/CVE-2022-0199/index.md)
```

## Sources

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

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