Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain high-privilege WordPress credentials
-
DeliveryAuthenticate to WordPress admin panel
-
ExploitNavigate to FluentCRM Pro author filter interface
-
ExecutionInject SQL payload into Author parameter
-
PersistExtract arbitrary database tables via SQL injection
-
ImpactExfiltrate CRM contacts, campaign data, and user credential hashes
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence 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 WordPress session with high-privilege (administrator-level) access to the FluentCRM Pro plugin, as confirmed by the PR:H metric in the CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:L vector. The specific vulnerable surface is the Author filtering or query parameter within the FluentCRM Pro administrative interface, so the attacker must have access to that specific feature. FluentCRM Pro must be installed and active on the target WordPress site. Factors that limit exploitation: (1) Only WordPress accounts with high-privilege roles (administrators or users explicitly granted FluentCRM admin capabilities) can reach the vulnerable parameter - lower roles such as Author, Editor, Subscriber, or Contributor are not in scope; (2) The I:N CVSS metric indicates the injection appears read-only, precluding direct database writes or schema modification via this vector alone; (3) Installations that have removed or restricted access to FluentCRM Pro's author filter functionality through role management plugins would reduce exposure. |
| Impact | The CVSS 7.6 High score is anchored by the scope change (S:C) and full confidentiality impact (C:H), but the PR:H requirement is the critical real-world mitigating factor - exploitation requires an already-authenticated, high-privileged user (WordPress administrator or equivalent), substantially shrinking the viable attack population compared to unauthenticated vulnerabilities. No EPSS score was included in the provided intelligence, leaving probabilistic exploitation frequency unquantifiable from base rates alone. The absence of a CISA KEV listing and lack of any reported public POC further suggest this is not under active or widespread exploitation. The primary realistic threat model is a compromised administrator account or malicious insider leveraging this injection to escalate data exfiltration scope beyond what FluentCRM Pro's own UI exposes. The I:N metric (no integrity impact) indicates a read-only injection pattern, limiting direct data manipulation. Overall assessment: treat as a routine patch-cycle priority; the PR:H gating means this does not warrant emergency out-of-band response for most organizations, but administrator credential hygiene is a co-critical control. |
| Exploit ScenarioDerived | An attacker with WordPress administrator credentials - obtained via phishing, credential stuffing against a reused password, or a prior site compromise - authenticates to the WordPress admin panel and navigates to the FluentCRM Pro campaign or contact interface. The attacker crafts a malicious Author parameter value containing SQL injection syntax (e.g., a UNION SELECT or time-based blind payload), which the plugin passes unsanitized to the database engine. The resulting query returns data from arbitrary tables across the WordPress database, allowing full extraction of CRM contact records, email campaign metadata, and wp_users password hashes. No public exploit code has been identified at time of analysis, but the AC:L rating indicates exploitation is technically straightforward for any attacker with administrative access. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 24, 2026
SQL injection in FluentCRM Pro (WordPress plugin, versions ≤ 3.1.12) allows network-accessible, high-privileged authenticated users to inject arbitrary SQL via the Author parameter, compromising full database confidentiality. The CVSS scope change (S:C) with C:H indicates successful exploitation extends read access well beyond the plugin's own tables - potentially exposing CRM contact records, campaign data, and WordPress user credential hashes stored in the underlying MySQL/MariaDB database. No public exploit code has been identified and this CVE is not listed in CISA KEV at time of analysis.
RemediationAI
The primary fix is to upgrade FluentCRM Pro to a version above 3.1.12 immediately, as all versions at or below this release are confirmed vulnerable. The exact patched version number must be verified directly against the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/fluentcampaign-pro/vulnerability/wordpress-fluentcrm-pro-plugin-3-1-12-sql-injection-vulnerability or the official WordPress plugin changelog, as an independently confirmed fixed release version was not present in the available intelligence. If an immediate upgrade is not feasible, reduce the number of accounts holding WordPress administrator privileges to the minimum necessary, since the PR:H CVSS metric confirms exploitation is limited to high-privileged sessions. Deploying a WAF with SQL injection detection rules (e.g., ModSecurity CRS) can serve as a compensating control, though SQL injection WAF bypasses are feasible for skilled attackers and should not be treated as a permanent substitute for patching. Database query logging with anomaly detection on UNION, SLEEP, or BENCHMARK keywords can aid in identifying exploitation attempts.
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
FluentCRM Pro is a premium WordPress CRM and email marketing automation plugin developed by WP Manage Ninja LLC, identified by CPE cpe:2.3:a:wp_manageninja_llc:fluentcrm_pro:*:*:*:*:*:*:*:*. The root cause is CWE-89 (Improper Neutralization of Special Elements in an SQL Command): the 'Author' parameter - likely a filter or query input within the plugin's campaign management or contact list interface - is not sufficiently sanitized before incorporation into backend SQL queries against the WordPress MySQL/MariaDB database. This permits injection of arbitrary SQL clauses, potentially enabling UNION-based data extraction, error-based enumeration, or time-based blind SQL injection to read from any table in the shared WordPress database schema.
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:L/PR:H/UI:N/S:C/C:H/I:N/A:L
Network-accessible WordPress plugin requiring administrator-level authentication (PR:H); scope change reflects cross-table database reads beyond plugin boundary; no integrity impact consistent with read-only SQL injection pattern.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Author SQL Injection in FluentCRM Pro <= 3.1.12 versions.
Executive ViewAI
A SQL injection vulnerability in FluentCRM Pro (WordPress plugin, versions ≤3.1.12) allows high-privileged authenticated users to compromise database confidentiality, potentially exposing CRM contact records, campaign data, and WordPress user credential hashes. No public exploit identified at time of analysis, but organizations using this plugin face elevated risk of data breach if administrative access is compromised.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) restrict database query privileges for the WordPress user account to minimum necessary operations; (2) deploy WAF rules to detect and block SQL injection syntax in Author parameter; (3) implement database activity monitoring with alerts for suspicious queries; (4) enforce principle of least privilege for WordPress administrative accounts; (5) maintain strict monitoring of vendor advisory channels for patch availability.
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
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Fluentcrm Pro
View allPrivilege escalation in FluentCRM Pro (WordPress plugin, versions <= 3.1.12) allows authenticated users holding the Edit
Server-Side Request Forgery in FluentCRM Pro (WordPress plugin by WP Manage Ninja LLC) versions up to and including 3.1.
EUVD-2026-64835
GHSA-gv84-hx59-95x6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB