CVE-2023-7202 json
Fatal Error Notify < 1.5.3 - Subscriber+ Test Error Email Sending
published 2024-02-27 2 y ago modified 2026-06-17 4 mo ago also EUVD-2023-59383
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
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
Patch / fix
- Unknown Fatal Error Notify 1.5.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/d923ba5b-1c20-40ee-ac69-cd0bb65b375a/ referenced PoC, tagged "exploit" by a source, unverified
- research.cleantalk.org https://research.cleantalk.org/cve-2023-7202-fatal-error-notify-error-email-sending-csrf/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L |
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L |
Affected products
- Unknown Fatal Error Notify
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
- Technology feeds
References
-
wpscan.com
/vulnerability/d923ba5b-1c20-40ee-ac69-cd0bb65b375a/
exploit, vdb-entry, technical-description, third-party-advisory
-
research.cleantalk.org
/cve-2023-7202-fatal-error-notify-error-email-sending-csrf/
exploit, third-party-advisory
Sources
- CVE List CVE-2023-7202
- NVD CVE-2023-7202
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.