# CVE-2023-7202: Fatal Error Notify < 1.5.3 - Subscriber+ Test Error Email Sending


- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Feb 2024
- **Updated:** 28 Oct 2024
- **Also known as:** GHSA-wp95-g3h2-jhqf

## What is CVE-2023-7202?

CVE-2023-7202 is a medium-severity vulnerability in Unknown Fatal Error Notify, published on 27 Feb 2024. 

### Official description

The Fatal Error Notify WordPress plugin before 1.5.3 does not have authorisation and CSRF checks in its test_error AJAX action, allowing any authenticated users, such as subscriber to call it and spam the admin email address with error messages. The issue is also exploitable via CSRF

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

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

It affects 1 product.


Products: Verygoodplugins Fatal Error Notify.

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

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

## Is CVE-2023-7202 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-7202 is a medium-severity vulnerability in Unknown Fatal Error Notify, published on 27 Feb 2024. 
Exploitation: There is no known exploitation of CVE-2023-7202 in the wild and no public exploit code.

Affected product: Unknown Fatal Error Notify. 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-7202/ (Markdown: https://insights.sbomify.com/CVE-2023-7202/index.md)
```

## Sources

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

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