CVE-2026-122063: Newsletters <= 4.18.2 - Authenticated (Subscriber+) SQL Injection via 'user_email' User Meta

Published Nov 13, 2026
·
Updated

The Newsletters plugin for WordPress is vulnerable to blind SQL Injection via the 'useremail' 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.

Affected Software

1 affected component
Tribulant Newsletters<=4.18.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Disable the admin-controlled 'currentusersubscribed' option to prevent this exploit path.

    Newsletters for WordPress currentusersubscribed = disabled

Event History

Nov 13, 2026
CVE Published
via MITRE·09:35 AM
Data Sourced
via MITRE·09:35 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·10:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue?

An authenticated WordPress user with Subscriber-level access or higher can exploit it. The attacker can update their own profile email address to a crafted value and then load a page containing the affected subscription interface.

2

What site configuration is required for exploitation?

The administrator-controlled currentusersubscribed option must be enabled. The site must also have at least one page that renders the Newsletters subscribe shortcode or widget.

3

What information could an attacker obtain?

The SQL injection is blind, but it can be used to extract sensitive information from the WordPress database. The provided impact information indicates confidentiality impact only, with no stated integrity or availability impact.

4

How can I determine whether my site is exposed?

Check whether the Newsletters plugin version is 4.18.2 or earlier, whether currentusersubscribed is enabled, and whether any page renders the Newsletters subscribe shortcode or widget. Sites lacking either required configuration condition are not described as exploitable by the provided information.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203