Live › vulnerability › CVE-2026-110185
Go to dashboardThe Bit Flows WordPress plugin up to version 1.31.0 lets an unauthenticated attacker make the server include and execute a local PHP file through a webhook body field passed to an ImageHelper node. Successful exploitation can bypass access controls, expose sensitive data, or run PHP code where PHP files can be uploaded and included.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 07:31 UTC. All times on this page are UTC.
Sites running the Bit Flows WordPress plugin at version 1.31.0 or earlier are exposed only if an administrator has built a webhook-triggered flow that passes a webhook body field into an ImageHelper imageToBase64 node, with the webhook left in its default configuration. Sites without such a flow, or with the webhook secured, are not exposed under the described conditions.
No product ranges from the sources yet.
wp plugin get bit-flows --field=version (the plugin slug is unknown from the sources; confirm it on the install).imageToBase64 node.1.31.0; the fixed version is unknown from the sources.imageToBase64 nodes.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-110185")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.