# CVE-2024-37098: WordPress BlossomThemes Email Newsletter plugin <= 2.2.6 - Server Side Request Forgery (SSRF) vulnerability

> An attacker can exploit a Server-Side Request Forgery vulnerability in the BlossomThemes Email Newsletter plugin to access internal resources or bypass security controls.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-h65f-46fv-r349

## What is CVE-2024-37098?

CVE-2024-37098 is a medium-severity server-side request forgery vulnerability in BlossomThemes Email Newsletter, published on 26 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Server-Side Request Forgery (SSRF) vulnerability in Blossom Themes BlossomThemes Email Newsletter.This issue affects BlossomThemes Email Newsletter: from n/a through 2.2.6.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Blossomthemes Blossomthemes Email Newsletter.

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

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

## Is CVE-2024-37098 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-37098 is a medium-severity server-side request forgery vulnerability in BlossomThemes Email Newsletter, published on 26 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-37098 in the wild and no public exploit code.

Affected product: BlossomThemes Email Newsletter. 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-37098/ (Markdown: https://insights.sbomify.com/CVE-2024-37098/index.md)
```

## Sources

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

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