Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber account
-
DeliveryAuthenticate to WordPress site
-
ExploitIdentify vulnerable FluentCRM Pro SSRF endpoint
-
ExecutionSubmit crafted request with internal target URL
-
PersistServer-side HTTP request reaches internal resource
-
ImpactExfiltrate response data (credentials, internal API responses)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V4 - API and Web Service URL allowlisting, SSRF prevention
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated session with at minimum WordPress subscriber-level privileges (CVSS PR:L), meaning the attacker must possess or be able to register a valid account on the target site - sites with open registration enabled face a broader attacker pool than invite-only or closed-registration deployments. The AC:H rating indicates an additional constraint beyond mere authentication, though the specific triggering condition (e.g., a particular plugin feature being active, a specific request structure) is not enumerated in the available description and should be confirmed via the Patchstack disclosure. Exploitation is limited to network-reachable WordPress installations; the server's outbound network egress determines the blast radius, with cloud-hosted instances on AWS/GCP/Azure facing the highest internal-resource exposure. Subscriber registration must be enabled on the WordPress site, or the attacker must already possess a low-privilege account obtained through other means. |
| Impact | The NVD-assigned CVSS 3.1 base score of 4.9 (Medium) reflects the constrained attack surface: AC:H signals that exploitation requires conditions beyond simple network reachability, and PR:L requires at minimum subscriber-level authentication, narrowing the attacker population to registered users. The scope change (S:C) with C:L and I:L indicates that while individual impact per request is bounded, the vulnerability can be used to probe or interact with internal infrastructure - cloud metadata endpoints (e.g., 169.254.169.254), internal APIs, or intranet services - representing a meaningful lateral-movement primitive in cloud-hosted WordPress environments. No EPSS score was provided, and the vulnerability has neither a KEV listing nor known public POC, suggesting exploitation is not currently widespread. Real-world risk is elevated for WordPress installations on cloud infrastructure where metadata services or internal APIs are reachable from the web server, and reduced for on-premises deployments with tight network egress controls. The AC:H rating should be independently verified with Patchstack's disclosure for the exact triggering condition. |
| Exploit ScenarioDerived | An attacker registers a subscriber account on a WordPress site running FluentCRM Pro (or obtains credentials for an existing subscriber), then submits a crafted request to the vulnerable plugin endpoint with a URL pointing to an internal cloud metadata service such as http://169.254.169.254/latest/meta-data/. The WordPress server fetches the resource and returns or processes the response, allowing the attacker to enumerate IAM role credentials or internal service endpoints. No public POC exists at time of analysis, but the attack pattern is well-understood for WordPress SSRF classes. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
Server-Side Request Forgery in FluentCRM Pro (WordPress plugin by WP Manage Ninja LLC) versions up to and including 3.1.12 allows low-privileged authenticated users holding the subscriber role to induce the WordPress server to make outbound HTTP requests to arbitrary internal or external destinations. The scope-changed CVSS vector (S:C) confirms the vulnerability can pivot beyond the WordPress application boundary to reach internal network services not otherwise exposed. No public exploit code or CISA KEV listing has been identified at time of analysis; EPSS data was not supplied.
RemediationAI
The primary remediation is to update FluentCRM Pro beyond version 3.1.12; consult the vendor changelog and the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/fluentcampaign-pro/vulnerability/wordpress-fluentcrm-pro-plugin-3-1-12-server-side-request-forgery-ssrf-vulnerability for the exact patched release version, as a specific fix version was not independently confirmed in the available data. If immediate patching is not possible, restrict subscriber-level registration on the WordPress site to prevent untrusted users from obtaining the PR:L foothold required for exploitation - note this may break legitimate CRM subscriber workflows. Additionally, enforce strict outbound HTTP egress filtering at the network perimeter or web application firewall layer to block requests from the WordPress server to cloud metadata endpoints (169.254.169.254, fd00:ec2::254) and RFC-1918 address ranges; this does not remove the vulnerability but significantly limits SSRF impact. For cloud-hosted instances, ensure IMDSv2 (AWS) or equivalent metadata service protections are enabled, which require session-oriented token headers that server-side SSRF typically cannot supply.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-918 (Server-Side Request Forgery) describes a class of flaws where user-controlled input is used to construct server-side HTTP requests without adequate URL validation or allow-listing. In WordPress plugins this typically occurs when a REST API endpoint or AJAX handler accepts a URL parameter and performs a wp_remote_get() or cURL call on it without restricting the target schema or host. The affected product is identified by CPE cpe:2.3:a:wp_manageninja_llc:fluentcrm_pro:*:*:*:*:*:*:*:* - FluentCRM Pro is a premium email marketing and CRM automation plugin for WordPress. The subscriber role is the lowest default WordPress authentication tier, meaning any registered site user (e.g., newsletter subscribers, WooCommerce customers) can potentially trigger the vulnerable functionality.
Know when Fluentcrm Pro gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:L/A:N
Subscriber auth (PR:L), unspecified high-complexity trigger (AC:H), and server-side pivot to internal resources justifies S:C with C:L/I:L; no availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Server Side Request Forgery (SSRF) in FluentCRM Pro <= 3.1.12 versions.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Server-Side Request Forgery exploits applications that fetch remote resources based on user-supplied URLs.
More in Fluentcrm Pro
View allSQL injection in FluentCRM Pro (WordPress plugin, versions ≤ 3.1.12) allows network-accessible, high-privileged authenti
Privilege escalation in FluentCRM Pro (WordPress plugin, versions <= 3.1.12) allows authenticated users holding the Edit
EUVD-2026-64784
GHSA-242g-gc8x-5mmf
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB