# CVE-2024-6172: SQL injection in Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress

> Unauthenticated attackers can exploit SQL injection to extract sensitive database information from the Email Subscribers by Icegram Express WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jul 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-x8hp-rjr5-68q5

## What is CVE-2024-6172?

CVE-2024-6172 is a critical SQL injection vulnerability in icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Email Subscribers by Icegram Express – Email Marketing, Newsletters, Automation for WordPress & WooCommerce plugin for WordPress is vulnerable to time-based SQL Injection via the db parameter in all versions up to, and including, 5.7.25 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. CVE-2024-37252 appears to be a duplicate of this issue.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-6172?

It affects 1 product.


Products: Icegram Email Subscribers \& Newsletters.

## How do I fix CVE-2024-6172?

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

## Is CVE-2024-6172 being exploited?

There is no known exploitation of CVE-2024-6172 in the wild and no public exploit code.

## Other vulnerabilities in icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress

- [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-2022-0439](https://insights.sbomify.com/CVE-2022-0439/): Email Subscribers & Newsletters < 5.3.2 - Subscriber+ Blind SQL injection (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-2024-6172 and fix it if it is affected.

What it is: CVE-2024-6172 is a critical SQL injection vulnerability in icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress, published on 2 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6172 in the wild and no public exploit code.

Affected product: icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress. 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-2024-6172/ (Markdown: https://insights.sbomify.com/CVE-2024-6172/index.md)
```

## Sources

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

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