CVE-2022-0439 json
Email Subscribers & Newsletters < 5.3.2 - Subscriber+ Blind SQL injection
published 4y ago modified 4mo ago also EUVD-2022-15578
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.2%
- EPSS 4.2% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
Patch / fix
- Unknown Email Subscribers & Newsletters 5.3.2
Is CVE-2022-0439 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
4.16% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Nuclei template Email Subscribers & Newsletters <= 5.3.1 - Authenticated SQL Injection nuclei detection template
- wpscan.com https://wpscan.com/vulnerability/729d3e67-d081-4a4e-ac1e-f6b0a184f095 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
Affected products
- Unknown Email Subscribers & Newsletters
Classification
- Weakness
- Technology feeds
References
-
wpscan.com
/vulnerability/729d3e67-d081-4a4e-ac1e-f6b0a184f095
exploit, vdb-entry, technical-description, third-party-advisory
Sources
- CVE List CVE-2022-0439
- NVD CVE-2022-0439
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.