# CVE-2022-0439: Email Subscribers & Newsletters < 5.3.2 - Subscriber+ Blind SQL injection

> Attackers can perform blind SQL injection and CSRF attacks via unescaped parameters in the Email Subscribers & Newsletters WordPress plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9j96-8p8g-j5gr

## What is CVE-2022-0439?

CVE-2022-0439 is a high-severity SQL injection vulnerability in Unknown Email Subscribers & Newsletters, published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2022-0439?

It affects 1 product.


Products: Icegram Email Subscribers \& Newsletters.

## How do I fix CVE-2022-0439?

No fix has been published for CVE-2022-0439 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-0439 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0439 exists.

Public exploit code:

- CVE-2022-0439 - Email Subscribers & Newsletters < 5.3.2 - Subscriber+ Blind SQL injection (github_poc): https://github.com/RandomRobbieBF/CVE-2022-0439
- Email Subscribers & Newsletters <= 5.3.1 - Authenticated SQL Injection (nuclei): http/cves/2022/CVE-2022-0439.yaml

## Other vulnerabilities in Unknown Email Subscribers & Newsletters

- [CVE-2024-6172](https://insights.sbomify.com/CVE-2024-6172/): SQL injection in Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress (critical 9.8)
- [CVE-2024-4295](https://insights.sbomify.com/CVE-2024-4295/): Email Subscribers by Icegram Express <= 5.7.20 - Unauthenticated SQL Injection via hash (critical 9.8)
- [CVE-2019-13569](https://insights.sbomify.com/CVE-2019-13569/): SQL injection in n/a (critical 9.8)
- [CVE-2022-3981](https://insights.sbomify.com/CVE-2022-3981/): Icegram Express < 5.5.1 - Subscriber+ SQLi (high 8.8)
- [CVE-2019-20361](https://insights.sbomify.com/CVE-2019-20361/): SQL injection in n/a (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-0439 and fix it if it is affected.

What it is: CVE-2022-0439 is a high-severity SQL injection vulnerability in Unknown Email Subscribers & Newsletters, published on 7 Mar 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-0439 exists.

Affected product: Unknown Email Subscribers & Newsletters. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-0439/ (Markdown: https://insights.sbomify.com/CVE-2022-0439/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-0439
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-0439
- OSV: https://osv.dev/vulnerability/CVE-2022-0439

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-0439/
Summaries are generated and may contain mistakes; the official description above is the record.