Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure authenticated admin to attacker page
-
ExploitBrowser auto-submits forged plugin request
-
ExecutionMissing CSRF nonce check passes
-
ImpactUnauthorized plugin action executed as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK
1 technique across 1 tactic: Initial 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 a victim who is already authenticated to the target WordPress site with sufficient privileges over FunnelKit Automations (typically an administrator or plugin operator) to be tricked into visiting attacker-controlled content while that session is active (UI:R). The attack is defeated by the normal WordPress nonce mechanism, so it only works against plugin actions that fail to validate a CSRF token; the specific vulnerable feature, endpoint, or configuration is not described in the available sources. Limiting factors: the mandatory user interaction and the need for a logged-in privileged victim mean this cannot be exploited against an unauthenticated or idle target, and no special non-default configuration is indicated as required. |
| Impact | This is a CWE-352 Cross-Site Request Forgery flaw in the FunnelKit Automations WordPress plugin (≤ 3.8.5.2), scored CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and reported by Patchstack with a vuln.today priority of 'this_week'. The signals are partially conflicting and partially absent. On the one hand, the CVSS vector is network-reachable with low complexity and no attacker-held privileges (PR:N, standard for CSRF since the privilege is supplied by the tricked victim) and claims High impact to confidentiality, integrity and availability. On the other hand, the mandatory UI:R requirement means a logged-in user must be socially engineered into visiting attacker content, which materially lowers real-world exploitability compared with a no-interaction RCE. There is no CISA KEV listing, no EPSS probability supplied, and no confirmed public exploit in the input, so there is no evidence of active or widespread exploitation - the 8.8 is a severity ceiling, not an exploitation-likelihood signal. Critically, the description does not state which plugin action the CSRF triggers, so the C:H/I:H/A:H impact rating is Patchstack's assumption rather than an evidenced fact; the true impact cannot be verified from the available sources. Net: a genuine, patch-worthy issue warranting remediation on the vendor's/triage 'this_week' cadence, but not an emergency given the user-interaction gate and absence of any exploitation evidence. |
| Exploit ScenarioDerived | An attacker crafts a malicious web page or email containing a forged request targeting a FunnelKit Automations endpoint and lures a currently authenticated WordPress user (typically an administrator) into opening it. Because the vulnerable action lacks proper anti-CSRF nonce validation, the victim's browser submits the request with their valid session, performing a state-changing operation without consent. The specific triggered action is not described in the available sources, and no confirmed working exploit code is listed - only a Patchstack database reference. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Cross-site request forgery in the FunnelKit Automations WordPress plugin (wp-marketing-automations) affects every release through 3.8.5.2 and lets an attacker induce a logged-in privileged user - typically an administrator or plugin operator - to submit state-changing requests against the site without their intent. The issue carries CVSS 3.1 score 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) because successful forgery can compromise confidentiality and integrity, but it cannot succeed without that victim interaction on an active, authenticated session. Reported by Patchstack and assigned a vuln.today priority of 'this_week'; no public exploit code and no confirmed active exploitation (CISA KEV) are indicated in the available data.
RemediationAI
No vendor-released patch version is identified in the provided sources, so the fixed release (any version above 3.8.5.2) must be confirmed against the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wp-marketing-automations/vulnerability/wordpress-funnelkit-automations-plugin-3-8-5-2-cross-site-request-forgery-csrf-vulnerability?_s_id=cve before upgrade claims are made. The sources do not identify the vulnerable endpoint or configuration, so no targeted compensating control (such as disabling a specific feature or restricting a specific route) can be prescribed from the available evidence; the stated limiting factors are only that exploitation requires a logged-in privileged victim and mandatory user interaction, meaning exposure ends once that session is not active or the user does not follow attacker-supplied content. Prioritization should follow the vuln.today decision label of 'this_week'; there is no CISA KEV entry and no confirmed working exploit code in the supplied data.
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 CWE-352 (Cross-Site Request Forgery) in a WordPress marketing-automation plugin. WordPress defends state-changing requests with per-action nonces, so a CSRF condition exists only for plugin actions that fail to validate that token; the available sources do not describe which feature, REST route, admin action, or AJAX handler is affected, so the exact trigger is not described. Exploitation therefore depends entirely on luring an already-authenticated privileged user to attacker-controlled content while their session cookie is live (UI:R in the assessed vector), and the vector's PR:N reflects the unauthenticated position of the attacker rather than any unauthenticated path into the plugin. The supplied CPE (cpe:2.3:a:aman:funnelkit_automations:*:*:*:*:*:*:*:*) is version-wildcarded, so the precise upper bound - 'through 3.8.5.2' - derives from the Patchstack advisory rather than from CPE range data.
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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CSRF gives PR:N with a mandatory tricked-victim click (UI:R) over the network (AV:N/AC:L); impact is retained as High per Patchstack but is unverified because the triggered action is not described.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Cross-Site Request Forgery (CSRF) vulnerability in Aman FunnelKit Automations wp-marketing-automations allows Cross Site Request Forgery.This issue affects FunnelKit Automations: from n/a through 3.8.5.2.
Articles & Coverage 1
Executive ViewAI
CVE-2026-111841 is a high-severity cross-site request forgery (CSRF) flaw in the FunnelKit Automations WordPress plugin that affects every release up to 3.8.5.2. Because no patch is yet available, and exploitation requires a privileged user-such as an administrator-to be induced to take an unintended action, the vulnerability could lead to unauthorized changes in confidential data and site integrity. This creates operational and reputational risk for organizations relying on this plugin for marketing automation, and leadership should prioritize mitigation to prevent potential compromise of administrative functions and brand trust.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the FunnelKit Automations plugin if not operationally critical, restricting administrative access with IP allowlisting and strong multi-factor authentication for privileged users, and deploying WAF rules to detect CSRF-style requests targeting the plugin. Monitor for suspicious administrative actions and review logs for unexpected changes.
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
Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.
Blind SQL injection in the WordPress plugin FunnelKit Automations (wp-marketing-automations) through version 3.8.5.2 let
Blind SQL injection in Views for WPForms WordPress plugin (versions ≤3.4.6) allows authenticated low-privilege attackers
Blind SQL injection in Ninja Forms Views plugin (versions ≤3.3.2) allows authenticated attackers with low-level privileg
The mintToken function of a smart contract implementation for aman, an Ethereum token, has an integer overflow that allo
Broken authentication in the FunnelKit Automations WordPress plugin (versions <= 3.7.3) allows authenticated low-privile
DOM-based cross-site scripting in the WordPress plugin CF7 Views - Complete Entry Management for Contact Form 7 (by Aman
Unauthenticated cross-site scripting in the CF7 Views - Complete Entry Management for Contact Form 7 WordPress plugin th
Stored cross-site scripting (XSS) in the CF7 Views - Complete Entry Management for Contact Form 7 plugin (versions <= 3.
EUVD-2026-109674
GHSA-8hx4-3v93-jhgx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB