Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain low-privileged WP account
-
DeliveryAuthenticate to Fluent CRM endpoint
-
ExploitAbuse incorrect privilege assignment
-
ExecutionEscalate to administrator capabilities
-
ImpactFull site compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Privilege assignment review
|
| Exploitation Conditions | Exploitation requires an authenticated WordPress account on a site running the Fluent CRM plugin version 3.2.5 or earlier (PR:L - a low-privileged user such as a subscriber/registered user, not an anonymous visitor). The flaw is an Incorrect Privilege Assignment (CWE-266) in the plugin's capability handling, so the practical prerequisite is that the target site both runs the vulnerable Fluent CRM version and permits the attacker to hold or self-register a low-level account (common on sites with open registration or membership features). Limiting factors: exploitation is NOT anonymous (some valid low-privilege credential or registration is needed) and requires the vulnerable plugin to be installed and active; no user interaction is required (UI:N) and no non-default configuration is named in the advisory. The description does not identify the exact vulnerable endpoint, action, or feature, so the specific request required could not be extracted from the provided data. |
| Impact | This is a genuine priority, not a high-CVSS-but-low-real-risk issue. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 8.8) describes a network-reachable, low-complexity privilege escalation requiring only a low-privileged authenticated account (PR:L) and no user interaction, yielding full confidentiality, integrity, and availability impact - consistent with CWE-266 (Incorrect Privilege Assignment), where a low-privileged WordPress user can elevate toward administrator. The signals are internally consistent: CVSS vector aligns with the description (authenticated privilege escalation). However, several real-risk signals are MISSING from the input: no EPSS exploitation-probability score was provided, the vulnerability is NOT in CISA KEV, no public POC was indicated, and no SSVC decision data was supplied - so exploitation status is 'no public exploit identified at time of analysis.' The practical risk driver is that WordPress plugins with many installed sites are attractive automated targets once a POC emerges, and the low bar (any subscriber/author-level account on a site allowing registration) makes post-disclosure exploitation plausible. Net: treat as a high-priority patch for any internet-facing Fluent CRM site that permits non-admin user accounts, while noting that current exploitation evidence is absent rather than confirmed. |
| Exploit ScenarioDerived | An attacker who holds or registers a low-privileged account (e.g., subscriber) on a WordPress site running Fluent CRM ≤ 3.2.5 sends an authenticated request that abuses the plugin's incorrect privilege assignment to grant themselves elevated capabilities, effectively escalating to administrator-level control of the site. No user interaction or victim action is required, and attack complexity is low. No public exploit code was identified in the provided data, so this scenario is inferred from the CVSS vector and CWE rather than a confirmed POC. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Privilege escalation in the Fluent CRM WordPress plugin version 3.2.5 and earlier allows an authenticated low-privileged user - such as a subscriber or self-registered account - to elevate their privileges and gain control over site resources, with a CVSS 3.1 score of 8.8 and high impact to confidentiality, integrity, and availability. Exploitation is not anonymous: it requires a valid low-privilege WordPress account plus an active vulnerable plugin installation, but no user interaction is needed (PR:L, UI:N) and no non-default configuration is named in the advisory. No public exploit identified at time of analysis; this is a genuine priority, not a high-CVSS-but-low-real-risk issue.
RemediationAI
No vendor-released patch identified at time of analysis, so there is no confirmed fixed version to install yet. If Fluent CRM's features are not essential, deactivating and removing the plugin is the most direct mitigation (trade-off: loss of CRM, email automation, and contact management functionality). If the plugin must stay active, close or heavily restrict open self-registration and membership sign-ups so attackers cannot obtain the low-privilege account the attack requires (trade-off: breaks public sign-up and membership onboarding flows), and audit existing low-privilege accounts to remove unnecessary ones (trade-off: possible user friction). Additional compensating controls are to restrict access to the plugin's administrative and settings endpoints to trusted IPs or administrator sessions via a WAF or reverse proxy, and to monitor wp_capabilities and user-role changes for unexpected privilege grants. Track the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/fluent-crm/vulnerability/wordpress-fluent-crm-plugin-3-2-5-privilege-escalation-vulnerability-2?_s_id=cve for an official fixed release.
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
The flaw is an Incorrect Privilege Assignment (CWE-266) in Fluent CRM's WordPress capability handling, meaning the plugin grants or fails to properly restrict a capability that should be reserved for higher-privileged roles, letting a low-privileged authenticated user perform privileged actions within the plugin. Per the CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, the attack surface is network-reachable with low attack complexity, requires low privileges (PR:L), needs no user interaction, and produces high impact across all three CIA metrics while the vulnerable component's scope remains unchanged. The affected product is identified by CPE cpe:2.3:a:wp_manageninja_llc:fluent_crm, covering Fluent CRM releases through 3.2.5. The advisory does not name the specific vulnerable endpoint, action, or feature, so the exact request required to trigger the escalation could not be extracted from the available data.
Know when Fluent Crm 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:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Authenticated low-privileged user (PR:L) exploits a network-reachable, low-complexity privilege escalation to administrator, giving full C/I/A impact with no scope change.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Incorrect Privilege Assignment vulnerability in WP ManageNinja LLC Fluent CRM fluent-crm allows Privilege Escalation.This issue affects Fluent CRM: from n/a through 3.2.5.
Executive ViewAI
Fluent CRM versions 3.2.5 and earlier expose organizations to a high-severity privilege escalation that allows authenticated low-privilege users, including self-registered subscribers, to gain control over site resources. Because no vendor patch is currently available, affected marketing, CRM, and customer-facing WordPress sites remain at risk of data compromise, unauthorized content changes, and service disruption. Leadership should prioritize inventory and mitigating controls for these sites due to the potential impact on customer trust, regulatory obligations, and business continuity.
No vendor-released patch identified at time of analysis; interim mitigations include deactivating or removing Fluent CRM 3.2.5 and earlier, disabling self-registration, restricting and auditing subscriber-level accounts, enforcing least privilege and MFA for administrators, monitoring for unauthorized privilege changes, and applying virtual patching or WAF rules if available.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
EUVD-2026-102026
GHSA-f9f3-3pfv-3qm3
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB