# CVE-2024-8771: Missing authorization in Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress

> Authenticated subscribers can access sensitive content from private, password-protected, and draft posts due to missing capability checks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **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:** 26 Sep 2024
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-pr27-f9rc-q4vm

## What is CVE-2024-8771?

CVE-2024-8771 is a medium-severity missing authorization vulnerability in icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress, published on 26 Sep 2024. Any signed-in user can exploit it over the network, 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 unauthorized access of data due to a missing capability check on the 'preview_email_template_design' function in all versions up to, and including, 5.7.34. This makes it possible for authenticated attackers, with Subscriber-level access and above, to extract sensitive data including the content of private, password protected, pending, and draft posts and pages.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Icegram Email Subscribers \& Newsletters.

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

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

## Is CVE-2024-8771 being exploited?

There is no known exploitation of CVE-2024-8771 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-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-2022-0439](https://insights.sbomify.com/CVE-2022-0439/): Email Subscribers & Newsletters < 5.3.2 - Subscriber+ Blind SQL injection (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8771 and fix it if it is affected.

What it is: CVE-2024-8771 is a medium-severity missing authorization vulnerability in icegram Email Subscribers & Newsletters – Email Marketing, Post Notifications & Newsletter Plugin for WordPress, published on 26 Sep 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-8771 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-8771/ (Markdown: https://insights.sbomify.com/CVE-2024-8771/index.md)
```

## Sources

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

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