CVE-2023-7195

Public Exploit

WP-Reply Notify <= 1.1 - Settings Update via CSRF

Description

The WP-Reply Notify WordPress plugin through 1.1 does not have a CSRF check in place when updating its settings, which could allow attackers to make a logged-in admin change them via a CSRF attack.

4.3

CVSS

Severity: Medium

CVSS 3.1 •

EPSS 0.10%

Affected: Unknown WP-Reply Notify

References

Link	Tags
https://wpscan.com/vulnerability/72279ca0-6365-4c83-adca-4d8e5808a8c5/	vdb entry exploit technical description

Frequently Asked Questions

What is the severity of CVE-2023-7195?: CVE-2023-7195 has been scored as a medium severity vulnerability.
How to fix CVE-2023-7195?: To fix CVE-2023-7195, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2023-7195 being actively exploited in the wild?: It is possible that CVE-2023-7195 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2023-7195?: CVE-2023-7195 affects Unknown WP-Reply Notify.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.