{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-7202 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-7202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-7202 is a medium-severity vulnerability in Unknown Fatal Error Notify, published on 27 Feb 2024."},"fix_prompt":"Check this codebase for CVE-2023-7202 and fix it if it is affected.\n\nWhat it is: CVE-2023-7202 is a medium-severity vulnerability in Unknown Fatal Error Notify, published on 27 Feb 2024. \nExploitation: There is no known exploitation of CVE-2023-7202 in the wild and no public exploit code.\n\nAffected product: Unknown Fatal Error Notify. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-7202/ (Markdown: https://insights.sbomify.com/CVE-2023-7202/index.md)","id":"CVE-2023-7202","markdown":"https://insights.sbomify.com/CVE-2023-7202/index.md","name":"CVE-2023-7202","record":{"aliases":["GHSA-wp95-g3h2-jhqf"],"analysis":null,"analysis_generated_by":null,"assigner":"WPScan","cpe":[{"product":"fatal_error_notify","vendor":"verygoodplugins"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Fatal Error Notify \u003c 1.5.3 - Subscriber+ Test Error Email Sending","id":"CVE-2023-7202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Smart Forms \u003c 2.6.87 - Subscriber+ Arbitrary Entry Deletion","id":"CVE-2023-7203"},"packages":[],"prev":{"headline":"Everest Backup \u003c 2.2.5 - Admin+ Arbitrary File Upload","id":"CVE-2023-7201"},"products":["Fatal Error Notify"],"published":"2024-02-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-28","vendors":["Unknown"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2023-7202/"}