Skip to main content

CartFlows EUVDEUVD-2026-89889

| CVE-2026-96837 HIGH
PHP Remote File Inclusion (CWE-98)
2026-09-30 Patchstack GHSA-x4pm-cppj-22vx
8.8
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Obtain Contributor account on target site
  2. Delivery
    Send crafted authenticated request to CartFlows
  3. Exploit
    Manipulate filename into PHP include/require
  4. Execution
    Trigger inclusion of attacker-controlled code
  5. Impact
    Execute arbitrary PHP as web server

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Command and Control

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 account at Contributor role or higher on a WordPress site running CartFlows version 3.2.0 or earlier (PR:L). No user interaction is needed (UI:N) and the attack is remote over the network (AV:N/AC:L). The practical limiting factor is obtaining Contributor access: sites that permit open/self-service registration or have multiple untrusted contributors are directly exposed, whereas single-author or closed-registration sites require the attacker to first compromise or acquire such an account. The specific configuration, feature, or endpoint that reaches the vulnerable PHP include is not disclosed in the available data.

Impact

This is a genuine priority. 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 flaw requiring only low privileges (a Contributor account) and no user interaction, yielding full confidentiality, integrity and availability impact - the classic signature of authenticated remote code execution on a web platform. CWE-98 (improper control of filename for include/require, i.e. PHP file inclusion / RFI-LFI) is consistent with the RCE claim and the 'LFI' tag. No EPSS score, CISA KEV listing, or public exploit code was provided in the input, so exploitation status is 'no public exploit identified at time of analysis' - this tempers immediacy but does not lower the intrinsic risk, since the barrier (any Contributor-level user on a site running an affected CartFlows version) is low on multi-author WordPress sites. The main limiting factor is that an attacker must already hold a Contributor (or higher) account, which narrows opportunistic mass exploitation to sites that allow untrusted registration or contributor signups. Data is single-source (Patchstack) with a sparse description that names neither the vulnerable parameter nor the include sink; the CVSS vector is the primary technical signal and should be treated as vendor/Patchstack-supplied rather than independently confirmed.

Exploit ScenarioDerived

An attacker registers or obtains a Contributor-level account on a WordPress site running CartFlows <= 3.2.0, then sends a crafted authenticated request that manipulates a filename passed to a PHP include/require, causing the server to include and execute attacker-influenced PHP. This yields remote code execution in the web server context and full compromise of the site. No public proof-of-concept was provided in the input.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.7% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Sep 30, 2026

Remote code execution in the CartFlows WordPress plugin affects versions 3.2.0 and earlier, allowing an authenticated user with Contributor role or higher to execute arbitrary code on the hosting server. The flaw is a PHP include/require path-control weakness (CWE-98) with a CVSS 3.1 score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation requires a valid low-privileged account but no user interaction. No public exploit was identified at time of analysis, and the practical exposure depends on whether the site grants Contributor access to untrusted users.

RemediationAI

Vendor-released exact fixed version is not specified in the provided intelligence; consult the Patchstack advisory for the fixed CartFlows release and ensure the plugin is upgraded beyond 3.2.0 to the latest patched version available from Brainstorm Force. If immediate upgrade is not possible, deactivate or remove the CartFlows plugin, accepting loss of checkout/funnel functionality, and restrict Contributor or higher accounts to trusted users, change default registration to Subscriber, and audit existing Contributor accounts, understanding these controls may disrupt editorial workflows. A WAF or virtual patching may reduce exploitability but cannot fully substitute for updating because the vulnerable endpoint is not disclosed. Confirm remediation guidance at https://patchstack.com/database/wordpress/plugin/cartflows/vulnerability/wordpress-cartflows-plugin-3-2-0-remote-code-execution-rce-vulnerability?_s_id=cve.

Affected VersionsENISA

CartFlows n/a ≤3.2.0

Affected Packages

euvd cartflows 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

CartFlows is a WordPress plugin, and the vulnerable code path involves improper control of a filename used in a PHP include/require statement (CWE-98), a class that can lead to local file inclusion or, under the right conditions, remote code execution. The provided CPE cpe:2.3:a:brainstorm_force:cartflows:*:*:*:*:*:*:*:* identifies Brainstorm Force's CartFlows as the affected product, and the Patchstack report tags PHP, WordPress, RCE, and LFI. The assessed vector (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) confirms the attack is network-reachable and needs only an authenticated Contributor-or-higher account; no user interaction is required, and the specific endpoint or configuration that reaches the vulnerable include is not disclosed in the available data.

Know when Cartflows 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 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-reachable file-inclusion RCE needing only a Contributor account (PR:L) and no interaction; code execution gives full C/I/A within the unchanged web-server scope.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

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

DescriptionCVE.org

Contributor Remote Code Execution (RCE) in CartFlows <= 3.2.0 versions.

Executive ViewAI

Why It Matters

The CartFlows plugin for WordPress, deployed on versions 3.2.0 and earlier, contains a remote code execution flaw that lets any account holding the Contributor role or higher run arbitrary code on the web server. Because Contributor-level access is often granted to freelancers, guest authors, or self-registered users, any organization hosting CartFlows is exposed if its user provisioning is not tightly controlled. Successful exploitation would give an attacker full control of the affected site and potentially the underlying hosting environment, risking customer data, brand trust, and regulatory exposure.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict or eliminate Contributor-and-above accounts for untrusted users, deactivate the CartFlows plugin on exposed sites, deploy WAF/virtual patching rules against PHP file-inclusion attempts, enforce least-privilege role reviews, restrict filesystem write permissions, and monitor for anomalous file changes and PHP execution in the plugin directory.

Threat Intelligence Overview

EPSS Score
0.7%
Top 47% exploitable
Prevalence
Medium
popular WordPress funnel-builder plugin by Brainstorm Force, large but not universal footprint
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 HIGH
CISA KEV No
Public POC No
EPSS 0.7%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
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
No
Human Impact
High
Technical Impact
Total

Priority Score

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

Attack Technique

Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

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