Email Subscribers & Newsletters - SQLi (CVE-2022-0439)
Description
The Email Subscribers & Newsletters WordPress plugin before 5.3.2 does not correctly escape the order and orderby parameters to the ajax_fetch_report_list action, making it vulnerable to blind SQL injection attacks by users with roles as low as Subscriber. Further, it does not have any CSRF protection in place for the action, allowing an attacker to trick any logged in user to perform the action by clicking a link.
psychologyCrowdSec Analysis
CVE-2022-0439 is a high-severity vulnerability in the Email Subscribers & Newsletters WordPress plugin that allows users with minimal privileges, such as Subscribers, to exploit a blind SQL injection flaw via improperly sanitized parameters. The lack of CSRF protection further enables attackers to trick logged-in users into executing malicious actions, potentially leading to unauthorized access, data leakage, or manipulation of the underlying database.
CrowdSec has been tracking this vulnerability and its exploits since 25th of March 2026.
CrowdSec has not observed any significant exploitation activity targeting CVE-2022-0439 across its network. As a result, no community-driven trend analysis is available for this vulnerability at this time.
Attackers exploit the /wp-admin/admin-ajax.php endpoint with the action=ajax_fetch_report_list parameter, injecting SQL payloads via the order parameter to perform authenticated SQL injection attacks against vulnerable WordPress sites.
Full Intelligence Available
Connect your API key to access CrowdSec scores, exploit timelines, and attacker IPs.
| Event | Date |
|---|---|
| CVE Published | 2022-03-07 |
| Rule Released | 2026-03-25 |
| CrowdSec First Seen | 2026-08-18 |
Related Weaknesses
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.