Description
The Bit Flows: AI Agent Automation & Integrations for Forms, CRM, eCommerce, Google Sheets, and More plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.31.0 via the 'image (any body field referenced by the ImageHelper node's mix tag)' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. Exploitation requires that an administrator has built a webhook-triggered flow that pipes a webhook body field into an ImageHelper imageToBase64 node, and that the webhook remains in its default configuration (no bearer secret enforced, no IP allowlist set) — a legitimate and documented use case.
Published: 2026-10-28
Score: 5.9 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Local File Inclusion leading to code execution
Action: Apply Patch
AI Analysis

Impact

The Bit Flows plugin contains a flaw that allows a malicious actor to include and execute arbitrary PHP files on the WordPress server by manipulating the 'image' field passed through an ImageHelper node when a webhook triggers a flow. This Local File Inclusion vulnerability (CWE‑98) enables the attacker to run arbitrary code by supplying a path to a PHP file that the application will include, thereby bypassing normal access controls. The impact rises from data exposure to full server compromise if the attacker can place and run PHP files on the file system.

Affected Systems

Affected systems are WordPress sites running the Bit Flows plugin in versions up to and including 1.31.0. The issue is tied to any webhook‑triggered flow that uses the ImageHelper’s imageToBase64 node with a body field that references an arbitrary image source. Site administrators using the default configuration—no bearer secret and no IP allowlist—are the most vulnerable.

Risk and Exploitability

The CVSS base score of 5.9 places the vulnerability in the medium impact range. No EPSS score is published, and the vulnerability is currently not listed in the CISA KEV catalog, indicating no publicly known exploits yet. However, the exploit requires only unauthenticated access to the webhook endpoint and a pre‑existing webhook flow, conditions that are documented and legitimate usage scenarios. Because the attacker can trigger the inclusion without additional credentials, the likelihood of exploitation remains significant, especially on sites with open or default webhook configurations.

Generated by OpenCVE AI on October 28, 2026 at 08:21 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Bit Flows to version 1.32.0 or later, where the image parameter validation is corrected.
  • Configure the webhook flow to enforce a bearer secret and enable an IP allowlist, ensuring only trusted traffic can trigger the flow.
  • Restrict file uploads on the WordPress instance to disallow PHP file types and remove any unintended paths that could be included by the plugin.

Generated by OpenCVE AI on October 28, 2026 at 08:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 28 Oct 2026 17:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Wed, 28 Oct 2026 07:00:00 +0000

Type Values Removed Values Added
Description The Bit Flows: AI Agent Automation & Integrations for Forms, CRM, eCommerce, Google Sheets, and More plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.31.0 via the 'image (any body field referenced by the ImageHelper node's mix tag)' parameter parameter. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included. Exploitation requires that an administrator has built a webhook-triggered flow that pipes a webhook body field into an ImageHelper imageToBase64 node, and that the webhook remains in its default configuration (no bearer secret enforced, no IP allowlist set) — a legitimate and documented use case.
Title Bit Flows: AI Agent Automation & Integrations for Forms, CRM, eCommerce, Google Sheets, and More <= 1.31.0 - Unauthenticated Local File Inclusion via 'webhook' and 'body' Parameters
Weaknesses CWE-98
References
Metrics cvssV3_1

{'score': 5.9, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: Wordfence

Published:

Updated: 2026-10-28T16:09:28.549Z

Reserved: 2026-10-13T17:19:23.777Z

Link: CVE-2026-110185

cve-icon Vulnrichment

Updated: 2026-10-28T14:36:45.155Z

cve-icon NVD

Status : Deferred

Published: 2026-10-28T07:16:46.203

Modified: 2026-10-28T16:17:00.570

Link: CVE-2026-110185

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-28T08:30:16Z

Weaknesses
  • CWE-98

    Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')