PatchTheCVECVE-2023-7195: The WP-Reply Notify WordPress plugin through 1.1 does not have a CSRF check in place when updating its setting
CVE-2023-7195 is a medium-severity flaw (CVSS 4.3) affecting wp-reply notify. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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.
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.2% (top 89%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2025-05-15 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-7195?
wp-reply notify: upgrade to newer than 1.1. Exact commands for each OS are on this page.
Is CVE-2023-7195 being exploited?
CVE-2023-7195 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-7195 affect?
CVE-2023-7195 affects wp-reply notify. Severity is medium (CVSS 4.3). 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.
How urgent is CVE-2023-7195?
Priority 23/100. Public exploit reference