WP-Reply Notify: Cross-site request forgery
WP-Reply Notify is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
- Component
- WP-Reply Notify
- Plugin slug
wp-reply-notify- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- May 15, 2025
This CVE was published May 15, 2025 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update WP-Reply Notify to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N