Read the docs
TI-2023-06581 Aliases CVE-2023-7195GHSA-rcp3-h3cv-rfv7

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

Priority MEDIUM 53CWE-352Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Tampering
Confidentiality · integrity · availability
None · Low · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA. Impact type from CWE-352.

Summary

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 it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00208 10th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA and NVD
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
UnknownWP-Reply Notifyup to 1.1—No fix listedCNA
  • WP-Reply Notify VendorUnknown Affected up to 1.1 Fixed in — No fix listed CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:ani2life:wp-reply_notify:*:*:*:*:*:wordpress:*:*up to 1.1VulnerableAni2life
  • cpe:2.3:a:ani2life:wp-reply_notify:*:*:*:*:*:wordpress:*:* Versions up to 1.1 Vulnerable ·Ani2life

Remediation

No fixed version listed by the sources yet.

Timeline

  1. 2026-10-02 Threatist record created from CVE-2023-7195
  2. 2026-10-03 Alias added: GHSA-rcp3-h3cv-rfv7

References

Sources