CVE-2026-7798

MediumCVSS 5.4

Published: 22/05/2026(UTC)Updated: 23/07/2026(UTC)Translated: 25/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.65%

47th percentile - higher than 47% of all known CVEs

Summary

The FluentCRM plugin for WordPress up to version 2.9.87 is vulnerable to blind SSRF via the 'SubscribeURL' parameter. Unauthenticated attackers can make requests to arbitrary locations from the application, allowing them to query and modify internal services. Exploitation requires that the SES bounce handling key has never been stored (default configuration).

Risk Assessment

An attacker can access internal network resources such as databases or API servers and potentially modify data, leading to confidentiality and integrity breaches.

Recommendation

Update the FluentCRM plugin to the latest version. If updating is not possible, configure SES bounce handling to generate a random key, which blocks unauthenticated requests.

Other vulnerabilities in FluentCRM

CVE-2025-12935Medium
The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'fluentcrm_content' shortcode in all versions up to, and including, 2.9.84 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS