ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2023-7195

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 v

Published May 15, 2025 · catalog updated May 20, 2025 · Unknown WP-Reply Notify

Check this week

CVE-2023-7195 is not in CISA KEV. FIRST estimates a 21.00% chance of exploitation in the next 30 days. Check whether you run Unknown WP-Reply Notify.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium4.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
21.00%
Remediation
Vendor / distro source
Affected products
vendor Unknown WP-Reply Notify 0 ≤1.1

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor Unknown WP-Reply Notify 0 ≤1.10 ≤1.1

How to fix CVE-2023-7195

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2023-7195 is not in CISA KEV. FIRST estimates a 21.00% chance of exploitation in the next 30 days. Check whether you run Unknown WP-Reply Notify.

Which versions are affected?

Compare what you have installed with Unknown WP-Reply Notify 0 ≤1.1 0 ≤1.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 21.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

WordPress security

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 15, 2025 · EUVD

    Detected

    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.

  2. May 20, 2025 · EUVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2023-7195

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2023-59376

    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.

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.