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

Q: 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.

Q: Is CVE-2026-7798 being exploited?

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

Q: 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.

Medium 5.4 Published 22 May 2026 Updated 22 May 2026

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

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

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

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.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

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: 1 Nuclei template.

Sources

Also known as GHSA-pq4x-338r-cq3h.