CVE-2026-7798 json
FluentCRM <= 2.9.87 - Unauthenticated Blind Server-Side Request Forgery via 'SubscribeURL' Parameter
published 5mo ago modified 3mo ago also EUVD-2026-31418
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 53%
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-7798 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5mo ago
Exploit prediction
0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N |
Affected products
- techjewel FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/5c3ca2d7-7af9-401f-bc5a-1796c6253cb0?source=cve
- plugins.trac.wordpress.org /browser/fluent-crm/trunk/app/Hooks/Handlers/ExternalPages.php#L113
- plugins.trac.wordpress.org /browser/fluent-crm/tags/2.9.87/app/Hooks/Handlers/ExternalPages.php#L113
- plugins.trac.wordpress.org /browser/fluent-crm/trunk/app/Hooks/Handlers/ExternalPages.php#L85
- plugins.trac.wordpress.org /browser/fluent-crm/tags/2.9.87/app/Hooks/Handlers/ExternalPages.php#L85
- plugins.trac.wordpress.org /browser/fluent-crm/trunk/app/Hooks/Handlers/ExternalPages.php#L87
- plugins.trac.wordpress.org /browser/fluent-crm/tags/2.9.87/app/Hooks/Handlers/ExternalPages.php#L87
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3532271%40fluent-crm&new=3532271%40fluent-crm&sfp_email=&sfph_m
Sources
- CVE List CVE-2026-7798
- NVD CVE-2026-7798
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.