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
Impact
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…
Source excerpt · WordfenceExploitation 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.
Affected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
bitpressadmin · Bit Flows: AI Agent Automation & Integrations for Forms, CRM, eCommerce, Google Sheets, and More
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 0 through 1.31.0 (inclusive) | affected |
Original source 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.
References
- Security advisory www.wordfence.com/threat-intel/vulnerabilities/id/d7ae89c1-d128-4b0c-ae70-69b0cd219382
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/app/src/Tools/ImageHelper/ImageHelperTool.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/app/src/Tools/ImageHelper/ImageHelperTool.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/app/src/Tools/ImageHelper/ImageHelperTool.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/app/HTTP/Controllers/WebhookDispatchController.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/hooks/api.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.31.0/backend/app/Helpers/Utility.php
- Source reference plugins.trac.wordpress.org/browser/bit-pi/tags/1.32.0/backend/app/src/Tools/ImageHelper/ImageHelperTool.php