Quick answers
- Is CVE-2026-13694 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-13694 being exploited in the wild.
- How severe is CVE-2026-13694?
- Informational severity, with a CVSS score of 6.5, published 21 July 2026.
- Which products and versions are affected?
- Bit Apps Bit Form < 3.1.0.
- Is there a fix for CVE-2026-13694?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-13694 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-13694?
- Check whether you run Bit Apps Bit Form at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass within the workflow-trigger mechanism of the Bit Form plugin. When a workflow's 1-hour trigger transient expires, the plugin fails to properly validate the provided trigger token. An unauthenticated attacker can exploit this by sending a crafted POST request to the 'bitforms_trigger_workflow' AJAX action with a non-empty, arbitrary token. If the attacker possesses a valid workflow log ID and entry ID, they can re-execute configured workflow actions such as email notifications and third-party integrations. This issue is fixed in version 3.1.0.
Affected products
- Bit Apps Bit Form < 3.1.0
Timeline
- 2026-06-30: disclosed: Publicly published by WPScan
- 2026-07-21: advisory: NVD published date