NEWSLETTERS · CVE-2026-122063 · Other
NO FIX YET
The Newsletters plugin for WordPress, in versions up to and including 4.18.2, builds a database query from the user_email parameter without proper escaping or preparation. An authenticated subscriber can append SQL to existing queries and extract sensitive data from the site database.
first public Nov 13, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites running the Newsletters WordPress plugin version 4.18.2 or older. Exploitation requires the 'currentusersubscribed' option to be enabled and a page showing the Newsletters subscribe shortcode or widget; sites without these can skip it. Attackers need a subscriber-level account, which open registration may allow.
Not affected if auth-required, default-config
Who cares newsletters-plugin, self-hosted, wordpress
4.18.2 and below are affected.No fix yet, per the sources.
The Newsletters plugin for WordPress is vulnerable to blind SQL Injection via the 'user_email' parameter in all versions up to, and including, 4.18.2 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. Exploitation requires the admin-controlled 'currentusersubscribed' option to be enabled and at least one page rendering the Newsletters subscribe shortcode or widget to exist; a Subscriber-level attacker can self-serve the attack by updating their own profile email to a crafted payload and loading such a page.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.