Strategic Overview
- Status
- Patched in 4.17
- Affected Plugin
- Newsletters
- Affected Version
< 4.17- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2026-17522
At a glance
CVE-2026-17522 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Newsletters WordPress plugin, affecting versions < 4.17. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.17; sites on affected versions should update now. Disclosed August 2026, reported by Erwan LR.
Vulnerability Overview
The Newsletters plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to 4.17. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Newsletters < 4.17 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Newsletters the fix is 4.17: builds < 4.17 are affected, anything from 4.17 onward is not.
Remediation
Update to version 4.17, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Newsletters: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Newsletters 4.17 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Newsletters
- 9.8CVE-2018-20987: Newsletters <= 4.6.8.5 Object Injection
CVE-2018-20987 - 9.1CVE-2024-32954: Newsletters <= 4.9.5 Arbitrary File Upload
CVE-2024-32954 - 8.8CVE-2024-8247: Newsletters <= 4.9.9.2 Privilege Escalation
CVE-2024-8247 - 8.8CVE-2019-14788: Newsletters <= 4.6.18 Directory Traversal
CVE-2019-14788 - 8.1CVE-2026-16267: Newsletters <= 4.15 PHP Object Injection
CVE-2026-16267 - 8.1CVE-2026-12583: Newsletters <= 4.14 PHP Object Injection
CVE-2026-12583 - 8.1CVE-2025-67911: Newsletters <= 4.11 PHP Object Injection
CVE-2025-67911 - 8.1CVE-2025-54034: Newsletters <= 4.10 Local File Inclusion
CVE-2025-54034
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C