# CVE-2026-7798: FluentCRM <= 2.9.87 - Unauthenticated Blind Server-Side Request Forgery via 'SubscribeURL' Parameter

> Unauthenticated attackers can perform blind SSRF to query or modify internal services if SES bounce handling is unconfigured.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2026
- **Updated:** 22 May 2026
- **Also known as:** GHSA-pq4x-338r-cq3h

## What is CVE-2026-7798?

CVE-2026-7798 is a medium-severity server-side request forgery vulnerability in techjewel FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.9.87 via the 'SubscribeURL' parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Exploitation requires that the SES bounce handling key ('_fc_bounce_key') has never been stored (i.e., the site is in its default/unconfigured state with respect to SES bounce handling) as visiting the bounce configuration page auto-generates and stores a random key that causes the authentication check to evaluate correctly and reject unauthenticated requests.

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

## Which versions are affected by CVE-2026-7798?


## How do I fix CVE-2026-7798?

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

## Is CVE-2026-7798 being exploited?

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

Public exploit code:

- WordPress FluentCRM <= 2.9.87 - Unauthenticated Blind SSRF (nuclei): http/cves/2026/CVE-2026-7798.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-7798 and fix it if it is affected.

What it is: CVE-2026-7798 is a medium-severity server-side request forgery vulnerability in techjewel FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution, published on 22 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-7798 exists.

Affected product: techjewel FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution. 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-2026-7798/ (Markdown: https://insights.sbomify.com/CVE-2026-7798/index.md)
```

## Sources

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

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