VYPR
Medium severity5.4NVD Advisory· Published May 22, 2026

CVE-2026-7798

CVE-2026-7798

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Unauthenticated blind SSRF in FluentCRM up to 2.9.87 via SubscribeURL parameter when the SES bounce key is not stored.

Vulnerability

Blind Server-Side Request Forgery exists in the FluentCRM plugin for WordPress versions up to and including 2.9.87 via the SubscribeURL parameter. The vulnerability is located in the SES bounce handler within ExternalPages.php. When the _fc_bounce_key option has never been set (site in default state), an unauthenticated request to route=bounce_handler with provider=ses bypasses the authentication check because the comparison $verifyKey !== $sesBounceKey fails when both are empty [1][2]. This allows an attacker to control a URL that the server will fetch, leading to blind SSRF.

Exploitation

An unauthenticated attacker sends a GET or POST request to the WordPress site with the parameters ?fluentcrm=1&route=bounce_handler&provider=ses&verify_key= (empty verify_key). Because the _fc_bounce_key option is not stored, the condition $verifyKey !== $sesBounceKey evaluates to false, and the plugin proceeds to process the bounce. The attacker then supplies a malicious SubscribeURL value, which the server will attempt to retrieve using its own HTTP client. No prior authentication or user interaction is required, and the site must be in its default unconfigured state regarding SES bounce handling.

Impact

Successful exploitation allows the attacker to make arbitrary outbound HTTP requests from the web server. This can be used to scan internal networks, query cloud metadata endpoints (e.g., AWS IMDS), or interact with internal services that accept HTTP requests. The SSRF is blind — the response contents are not directly returned to the attacker, but errors or side effects can be observed. The attack is constrained to TCP ports and protocols supported by WordPress's HTTP API.

Mitigation

The vendor addressed this vulnerability in FluentCRM version 2.9.88 (release date not publicly specified in the available references). Users should update immediately. If updating is not possible, ensure the SES bounce handling key is configured by visiting the bounce configuration page at /wp-admin/admin.php?page=fluentcrm-admin#/settings/bounce, which auto-generates and stores a random _fc_bounce_key. Once stored, the authentication check will properly reject unauthenticated requests. This vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog at the time of publication.

AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

8

News mentions

0

No linked articles in our index yet.