Skip to main content

FunnelKit Automations CVE-2026-111411

| EUVDEUVD-2026-112065 CRITICAL
SQL Injection (CWE-89)
2026-10-28 Patchstack GHSA-xxrj-fj77-w6c3
9.3
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Locate site running FunnelKit Automations
  2. Delivery
    Send crafted SQL injection payload
  3. Exploit
    Observe blind response differences
  4. Execution
    Infer and extract database records
  5. Impact
    Harvest WordPress credentials and PII

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

The affected product is the FunnelKit Automations (wp-marketing-automations) WordPress plugin at versions from an unspecified start through 3.8.5.2. The available sources do not name the specific parameter, AJAX action, REST route, or plugin feature through which the SQL injection is triggered, so the precise trigger is not described in the available sources and cannot be stated as a concrete prerequisite. As scored (AV:N/AC:L/PR:N/UI:N), exploitation needs no authentication and no user interaction against a reachable installation; however, this unauthenticated rating is not confirmed by the description, and WordPress plugin SQLi flaws are commonly limited to authenticated low-privilege roles - this is the key limiting factor defenders should verify with the vendor, since if authentication is in fact required, real-world exposure is substantially narrower than the raw score suggests.

Impact

This is a genuine high-priority issue, not a high-CVSS/low-real-risk case. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable flaw of low attack complexity requiring no privileges and no user interaction, which for a WordPress plugin means any internet-facing site running FunnelKit Automations is reachable by an unauthenticated remote attacker; combined with the base score of 9.3 and the vuln.today 'act_now' decision label sourced from Patchstack, remediation should be treated as urgent rather than deferred. The exploitation signals are partly incomplete and partly internally inconsistent: no EPSS probability was supplied, so widespread-versus-targeted exploitation likelihood cannot be quantified; the CVE is not listed in CISA KEV in the provided data, so there is no confirmation of active exploitation; and the only reference is a Patchstack advisory database entry, which documents the vulnerability but is not verified working exploit code. One concrete inconsistency to verify: the supplied vector sets S:C, C:H, I:N and A:L, yet the flaw is described purely as Blind SQL Injection (CWE-89), for which impact is normally confidentiality-dominated (data inference) with scope typically unchanged - the A:L (availability) component and the scope change are not explained by the description and should be confirmed against the Patchstack advisory. The PR:N (unauthenticated) rating also drives much of the score but is not corroborated by the description, which names no endpoint or privilege level; WordPress plugin SQLi flaws are frequently reachable only by authenticated low-privilege roles, so the unauthenticated assumption materially affects real-world exposure and warrants vendor verification.

Exploit ScenarioDerived

A remote attacker sends crafted HTTP requests containing malicious SQL fragments to the vulnerable FunnelKit Automations input, and because the injection is blind, infers database contents bit-by-bit from differences in application responses or timing, progressively extracting sensitive WordPress data such as user records, password hashes, and session or API secrets. The CVSS vector rates this as low-complexity and, as scored, unauthenticated, so no special attacker position is needed; however, no verified working exploit code was identified in the supplied sources - only a Patchstack advisory reference.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 28, 2026

Blind SQL injection in the WordPress plugin FunnelKit Automations (wp-marketing-automations) through version 3.8.5.2 lets remote attackers pass crafted SQL through a plugin input and infer database contents, exposing WordPress user credentials, session tokens and stored marketing/automation data. The vulnerability carries a 9.3 vendor-side CVSS score, while the independent assessment scores it as scope-unchanged with high confidentiality impact only (no integrity or availability effect); because the sources do not name the vulnerable parameter, AJAX action or REST route, the unauthenticated (PR:N) rating cannot be confirmed from the description, and WordPress plugin SQLi flaws are frequently limited to low-privilege authenticated roles - verifying that prerequisite is the decisive exposure question. No public exploit code has been identified at time of analysis, but the issue is flagged act_now priority and a public PoC reference may appear quickly given the plugin's wide install base.

RemediationAI

No vendor-released patch is identified in the available data at time of analysis: the record lists affected versions through 3.8.5.2 but does not name a fixed release, so administrators should check the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/wp-marketing-automations/vulnerability/wordpress-funnelkit-automations-plugin-3-8-5-2-sql-injection-vulnerability?_s_id=cve) and the plugin's WordPress.org/GitHub release notes for a version above 3.8.5.2 rather than assuming one exists. Because the injectable parameter or route is not disclosed, targeted virtual patching is not possible until a signature is published; the practical interim options are to constrain who can reach plugin functionality - for example restricting the plugin's admin-side and any automation endpoints by IP or role at the web server or WAF layer - with the trade-off that without knowing the vulnerable route such rules will produce false negatives and can break legitimate automation, email and CRM sync traffic, and to deactivate the plugin entirely on sites that do not depend on it, accepting loss of marketing automation. Confirm with the vendor whether the injection requires an authenticated low-privilege session, since if it does, tightening role assignments and auditing accounts with subscriber-level access meaningfully narrows exposure; enable database query logging and review for anomalous boolean- or time-based patterns as a detection measure while awaiting a fixed build.

Affected VersionsENISA

FunnelKit Automations 0 ≤3.8.5.2

Affected Packages

euvd funnelkit_automations no fix

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 CWE-89, improper neutralization of special elements in SQL commands, in a commercial WordPress marketing-automation plugin distributed as wp-marketing-automations and tracked under CPE cpe:2.3:a:aman:funnelkit_automations. The injection is described as blind, meaning the attacker does not receive query output directly and must extract data through boolean- or time-based inference against the WordPress database, which typically shares the same MySQL/MariaDB instance as the WordPress core tables (wp_users, wp_usermeta, wp_options). The CNA score of 9.3 uses S:C (scope changed) with C:H/I:N/A:L, whereas the independent assessment treats the boundary as unchanged (S:U) with C:H and no integrity or availability impact; either way the confidentiality exposure is the dominant risk, since dumped password hashes and authentication cookies/keys can be cracked or replayed. Critically, the available sources do not identify which plugin feature - an AJAX handler, admin-ajax action, REST route, shortcode or query parameter - carries the injectable input, so the trigger is not described in the available sources; WordPress plugin SQLi issues are often reachable only by logged-in users with minimal capabilities, and that gating is unverified here.

Know when Aman 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

Vendor (Patchstack) PRIMARY 9.3 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 7.5 HIGH

Network-reachable, low-complexity SQLi; blind read-only data inference gives C:H with no established integrity or availability impact, and I keep S:U absent evidence of a cross-authority scope change.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Aman FunnelKit Automations wp-marketing-automations allows Blind SQL Injection.This issue affects FunnelKit Automations: from n/a through 3.8.5.2.

Executive ViewAI

Why It Matters

A critical blind SQL injection vulnerability in the FunnelKit Automations WordPress plugin (through version 3.8.5.2) could allow remote attackers to extract sensitive data, including WordPress user credentials, session tokens, and marketing automation records. This affects all organizations using the vulnerable plugin, and while exploitation is not yet confirmed, the wide install base makes it an attractive target for attackers. Leadership should act promptly to mitigate potential data breaches and credential theft that could cascade into broader network compromise.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: restrict access to the plugin's endpoints via WAF rules blocking SQL injection patterns; enforce least privilege and review user roles; monitor database and outbound traffic for signs of exfiltration; consider temporarily disabling the plugin if not critical.

Threat Intelligence Overview

Prevalence
Medium
popular WordPress marketing-automation plugin, moderate install base
Social Media
2
Sightings
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS N/A
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy